MCP Discovery

ToolYour MCP uses progressive disclosure so agents never load hundreds of tool schemas at once.

Start with solve_task

Call solve_task(goal) first. If the server cannot auto-route, the response includes toolSuggestions (tools pre-searched from your goal) and points you to discover_tools.

Meta-tools (free)

Search tips

• Be specific: docx pdf beats convert
• Call list_categories first, then discover_tools(query, category) to narrow results
• Keep limit low (default 10) to minimize tokens
• After discovery: get_tool_schema → invoke_tool

What is excluded

Only tools with hasApi: true appear in MCP. Client-side calculators and UI-only utilities on toolyour.com are not available via MCP or REST API keys.

If you invoke a non-API tool you get:

{
  "error": {
    "code": "tool_not_api_backed",
    "message": "Tool not available for API / MCP"
  }
}

Recommended agent pattern

solve_task(goal) → (if suggest) toolSuggestions OR discover_tools("docx pdf") → get_tool_schema → invoke_tool

list_categories() → discover_tools("pdf", category: "Documents") → get_tool_schema → invoke_tool

Keep limit low (default 10) to minimize tokens.

Categories

Use list_categories() then discover_tools(query, category) to narrow results. Example categories: Convertors, Documents, SEO Tools, Text Intelligence.

See Calling tools for REST parity and MCP skills for playbooks.