Skip to main content
Glama
smart-mcp-proxy

mcpproxy-go

by smart-mcp-proxy
OverviewSchemaRelated ServersScoreDiscussions
Go
Local

retrieve_tools

Read-onlyDestructive

Search across all connected MCP servers using natural language to discover relevant tools. Always call this before using any other tool to find the right tool for your task.

Instructions

🔍 CALL THIS FIRST to discover relevant tools! This is the primary tool discovery mechanism that searches across ALL upstream MCP servers using intelligent BM25 full-text search. Always use this before attempting to call any specific tools. Use natural language to describe what you want to accomplish (e.g., 'create GitHub repository', 'query database', 'weather forecast'). Results include 'annotations' (tool behavior hints like destructiveHint) and 'call_with' recommendation indicating which tool variant to use (call_tool_read/write/destructive). Then use the recommended variant with an 'intent' parameter. NOTE: Quarantined servers are excluded from search results for security. Use 'quarantine_security' tool to examine and manage quarantined servers. TO ADD NEW SERVERS: Use 'list_registries' then 'search_servers' to find and add new MCP servers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
debugNoEnable debug mode with detailed scoring and ranking explanations (default: false)
explain_toolNoWhen debug=true, explain why a specific tool was ranked low (format: 'server:tool')
include_statsNoInclude usage statistics for returned tools (default: false)
limitNoMaximum number of tools to return (default: configured tools_limit, max: 100)
queryYesNatural language description of what you want to accomplish. Be specific about your task (e.g., 'create a new GitHub repository', 'get weather for London', 'query SQLite database for users'). The search will find the most relevant tools across all connected servers.

Tool Definition Quality

A4/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description portrays a read-only search tool, but annotations set destructiveHint: true, creating a direct contradiction. The description does not address this conflict, and the agent is left with inconsistent safety information. Annotation contradiction flagged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the critical purpose and usage guidance in the first sentence. While comprehensive, every sentence adds unique value (examples, notes, alternatives). Structure is logical and scannable, earning a top score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, usage, results content, and edge cases (quarantined servers, server addition). However, without an output schema, it does not fully detail the result structure or pagination, leaving a minor gap for a medium-complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by providing concrete query examples (e.g., 'create GitHub repository') and clarifying defaults for limit and debug. This goes beyond the schema's own descriptions, warranting a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is the primary tool discovery mechanism, using BM25 search across all servers. It gives a specific verb ('discover relevant tools') and resource ('tools'), and distinguishes itself from siblings like call_tool_read/write by being the prerequisite step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to call this first before any specific tools, explains how to use natural language queries, and notes the recommended variant usage. It also provides alternatives for quarantined servers and new server addition, making when-to-use vs. when-not-to-use very clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smart-mcp-proxy/mcpproxy-go'

If you have feedback or need assistance with the MCP directory API, please join our Discord server