Skip to main content
Glama

search_tools

Search tools across all connected sources and return full input schemas when 10 or fewer match. Use an empty query to list every available tool.

Instructions

Search tools across all connected sources. Returns full input schemas when 10 or fewer match. An empty query lists every tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, but it does disclose a genuinely useful behavioral trait: response richness varies with match count ('full input schemas when 10 or fewer match'). It omits what happens above 10 matches (truncated schemas? pagination?), whether there is a default result cap, and whether matching is keyword or semantic.

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 short sentences, each carrying distinct information, with the core purpose front-loaded and no filler. Nothing is redundant or padded.

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

Completeness3/5

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

For a 3-parameter tool with no output schema and no annotations, the description covers purpose, one key parameter, and partial return behavior. It leaves the agent guessing about `limit` and `source` behavior and about results beyond the 10-match threshold, which is a real gap for a discovery tool agents will call repeatedly.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters (limit, query, source) are undocumented in structured data. The description only explains query semantics (empty = list all); limit and source, both of which materially change results, receive no explanation of units, defaults, or accepted values.

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

Purpose4/5

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

The description states a specific verb and resource ('Search tools') plus scope ('across all connected sources'), which is enough to distinguish it from data-oriented siblings like search_context or read_memory. It stops short of naming an alternative or contrasting with list_connections explicitly.

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

Usage Guidelines3/5

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

It gives one concrete usage path ('An empty query lists every tool') that tells the agent how to enumerate rather than search. It does not say when to prefer this over search_context, call_tool, or list_connections, so routing between siblings is left to inference.

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