​

Errors

​

MCP errors

Tool input and business failures are returned as MCP tool errors so the calling model can inspect and correct them. Common identifiers include:

• model_capability_not_found
• mcp_models_and_categories_are_mutually_exclusive
• mcp_model_filter_limit
• mcp_category_filter_limit
• mcp_typed_tool_limit

​

Retry decisions

Do not blindly retry a paid failure. Submission retries are not deduplicated and may create another task and charge. Inspect the normalized error and confirm whether the original request created a task before resubmitting.

​

Tools are missing

Restart the MCP server or begin a new client session after changing its URL or filters. Confirm that models and categories are not used together and that the typed-tool limits are not exceeded.

​

Chat is not streaming

This is expected for poyo_chat: it returns one complete Tool Result. Use a native chat REST endpoint or poyo chat --stream for token SSE.

​

A task appears stuck

Keep the task ID and check it again with backoff. A client timeout or disconnect does not imply that the remote task failed. Contact support with the task ID if its status does not change beyond the model’s expected processing window.