Skip to main content
Glama

Search tools

search_tools
Read-onlyIdempotent

Find the hub's tools by what you want to do. Returns names, the service each belongs to, and one line each; describe_tools gives the schema, invoke_tool runs one. Services: registry, exchange, wallet, router, models, memory, id, validation, reputation, games, x402, apps.

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
limitNoMost tools to return
queryNoWhat you want to do, in words
serviceNoOnly tools of this service

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Most tools to return"
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / minimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
  3. Added

TDQS

A4.6/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 genuinely useful behavior beyond that – the shape of the result (name, service, one-line summary) – but is silent on match semantics (keyword vs semantic) and how limit behaves, which are the remaining unknowns.

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, front-loaded with purpose, then return shape, then alternatives and valid service values. Nothing is redundant or padded.

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?

With no output schema, the description correctly steps in to describe the return fields, and all three parameters are covered. Minor gaps remain – no default or ceiling for limit, and no statement of how query matching works – but the definition is sufficient to call the tool correctly.

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 the baseline is 3. The description earns the extra point by enumerating the valid service values (registry, exchange, wallet, router, models, memory, id, validation, reputation, games, x402, apps), which the schema does not provide as an enum and which the agent otherwise could not guess.

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 the hub's tools by what you want to do') and describes exactly what comes back: names, owning service, and a one-line summary. It also explicitly separates itself from describe_tools and invoke_tool, so an agent can pick the right one without opening a 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?

The definition lays out the routing chain: this tool to find, describe_tools for the schema, invoke_tool to execute. It also gives the concrete service list that can be used with the service filter, which is actionable guidance rather than inference.

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.