Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

search_mcp_servers

Read-only

Find MCP servers in the directory.

Searches the standalone MCP directory (official MCP Registry, Smithery,
Agenstry and other crawled sources) unioned with x402 services that also
expose an MCP endpoint.
Returns normalised entries with a ready-to-use streamable-http
`call_hint.mcp.url`.

Args:
    intent: Natural-language description of the tool/capability needed.
    top_k: Max servers to return (1-20).
    chain: Optional payment-network filter for paid MCP servers.
    require_healthy: When true, only return servers marked health=ok.
    scope: "remote" (default) = servers with an endpoint you can call now;
        "code" = code-only servers (repository / package you install and
        run yourself, no remote endpoint); "all" = both.

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_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional payment-network filter for paid MCP servers.
scopeNo"remote" (default) = servers with an endpoint you can call now; "code" = code-only servers (repository / package you install and run yourself, no remote endpoint); "all" = both.remote
top_kNoMax servers to return (1-20).
intentNoNatural-language description of the tool/capability needed.
require_healthyNoWhen true, only return servers marked health=ok.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scope
      Added value: +{
      +  "default": "remote",
      +  "description": "\"remote\" (default) = servers with an endpoint you can call now; \"code\" = code-only servers (repository / package you install and run yourself, no remote endpoint); \"all\" = both.",
      +  "title": "Scope",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description only needs to add context, and it does: it discloses the multi-source aggregation (official registry, Smithery, Agenstry, crawled sources, x402), the normalisation of results, and the presence of a ready-to-use streamable-http URL. It omits ranking behaviour and any rate/limit characteristics, which keeps it from a 5.

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

Conciseness3/5

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

The purpose is front-loaded and clear, but the trailing Args block duplicates the input schema almost word-for-word and adds length without information. Trimming it would leave a tighter, equally complete definition.

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?

An output schema exists, so return values need not be explained, and the description still usefully notes the call_hint.mcp.url shape. Combined with the corpus and scope explanation, an agent has what it needs to call the tool correctly; only ranking and result-volume behaviour are unstated.

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 description coverage is 100%, so the schema already documents all five parameters, and the Args block largely restates those descriptions verbatim rather than adding meaning. Baseline 3 applies; no extra syntax, format, or interaction details are supplied.

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?

States a specific verb and resource ('Find MCP servers in the directory') and clarifies the corpus searched: the standalone MCP directory unioned with x402 services exposing an MCP endpoint. That scope detail separates it conceptually from A2A/agent or generic resource search, but no sibling is named explicitly, so it stops short of full differentiation.

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?

The scope explanation ('remote' = call now, 'code' = install and run yourself) gives the agent a real decision rule for picking a mode, and require_healthy implies a quality gate. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as get_mcp_server for follow-up detail or the A2A/resource search siblings.

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.