mcp-toolsearch-proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| call_read_toolA | Call a tool that only reads (readOnly in search_tools results), with arguments matching the input schema from search_tools or describe_tool. Returns the tool's own result, or, when the arguments do not fit, what is wrong and the schema. Tools that may change anything are refused: call those with call_write_tool. |
| call_read_toolsA | Call up to 10 tools that only read (readOnly in search_tools results) at once, in parallel: each entry of calls is a name and arguments, as call_read_tool takes them. Returns every call's result in order, each labelled with its number, its tool and whether it failed; one that fails does not stop the others. Tools that may change anything are refused. |
| call_write_toolA | Call a tool that may create, change or delete something (not readOnly in search_tools results), with arguments matching the input schema from search_tools or describe_tool. Returns the tool's own result, or, when the arguments do not fit, what is wrong and the schema. Prefer call_read_tool for tools that only read. |
| describe_toolA | Return the full description and input schema of tools found with search_tools. |
| search_toolsA | Find the tools that can do what you describe, among all the tools you may use. Returns names and short descriptions, best match first, with the input schemas of the best few; read the input of any other with describe_tool. Give queries instead of query to find several things at once, such as a tool for the task and one for a value the user did not give. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role in the proxy workflow: search_tools discovers tools, describe_tool returns schemas, call_read_tool and call_read_tools execute single vs batch read-only calls, and call_write_tool executes mutating calls. The singular/plural read pair is the only close pair, but their batch-vs-single distinction is explicit in the descriptions.
All names follow a consistent snake_case verb_noun pattern: search_tools, describe_tool, call_read_tool, call_read_tools, call_write_tool. The plural suffix on call_read_tools is a readable and intentional variation for batching.
Five tools is well-scoped for a proxy server whose job is to discover, inspect, and invoke other tools. Each tool earns its place, with no redundant surface area.
The surface covers discovery, schema inspection, single and batch read execution, and write execution, which are the core operations for this proxy domain. Minor gaps include no batch write operation and no explicit enumerate-all-tools call, though search_tools can approximate discovery.