Skip to main content
Glama

Search tools across MCP servers

search_tools
Read-onlyIdempotent

Use when the user needs a specific capability (a tool) rather than a whole server; to find servers by topic use search_servers. Find individual tools by name and description (as the servers report them in tools/list), with the server each belongs to and its measurements. Example: q='pdf table extraction'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWords, max 200 characters
authNoAuthentication at the last check
riskNoDeclared by the server's tool hints
limitNoAsk only for as many results as needed (default 10)
offsetNo
categoryNoCategory ID, e.g. finance.crypto (see list_categories)
reachableNotrue = answered at the last check
transportNo
capabilityNoDeclared at initialize
min_success_7dNoDaily check success over 7 days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Ask only for as many results as needed (default 10)"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful context beyond that: results are per-tool entries carrying the owning server and its measurements, sourced from tools/list as servers report them. It does not discuss pagination behavior or result ordering, so not a full 5.

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?

Three tight clauses: the when-to-use routing, the disambiguation from search_servers, and one concrete example. Nothing is wasted and the selection guidance is front-loaded before the mechanics.

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?

For a 10-parameter search tool with no output schema, the description adequately conveys what is returned (tools plus owning server and measurements). Filters are carried by schema descriptions, which is fine; the only gap is that result ordering and pagination interplay (limit/offset) are not addressed.

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

Parameters3/5

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

Schema coverage is 80% with 10 params, so the schema already documents q, auth, risk, limit, category, reachable, capability and min_success_7d. The description adds a query-style example but says nothing about how the filter parameters combine (offset transport, risk enum semantics), leaving the baseline 3 appropriate.

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?

States a specific verb and resource ('Find individual tools by name and description') and explicitly scopes it against the sibling search_servers ('to find servers by topic use search_servers'). An agent can distinguish this from search_servers and list_categories without opening any schema.

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?

Gives an explicit when-to-use condition ('when the user needs a specific capability (a tool) rather than a whole server') and names the alternative tool plus the condition that selects it. The q example ('pdf table extraction') further grounds the intended usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources