Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

by io.github.AgentTools-Cloud

search_mcp_servers

Find MCP servers in the directory.

Searches the standalone MCP directory (PulseMCP / official MCP registry
import) 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo
top_kNo
intentNo
require_healthyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the core behavior (search directory, union sources, return normalized entries with URLs) but omits potential side effects, authentication needs, or rate limits. The description is adequate but could be more transparent about dependencies like network access or API keys.

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?

The description is concise and well-structured: a one-sentence summary followed by a paragraph detailing sources and output, and a bulleted list of parameters. Every sentence adds value, and no redundant information is present.

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?

Given the tool's moderate complexity (4 params, no required, has output schema), the description covers purpose, parameters, and output hint. It is nearly complete, but could mention if authentication or network access is required, especially since annotations are absent. The presence of an output schema reduces the need to detail return values.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It does so with a detailed 'Args' section that explains each parameter: 'intent' as natural-language description, 'top_k' with range (1-20), 'chain' as payment-network filter, and 'require_healthy' as filter for health=ok. This adds substantial meaning beyond the bare schema.

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?

The description clearly states 'Find MCP servers in the directory' and elaborates on the sources (standalone MCP directory unioned with x402 services). It specifies the output: normalised entries with a streamable-http URL. This distinguishes it from sibling tools like 'search' or 'get_mcp_server' by mentioning the unioned sources and the specific URL format.

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 description implies usage via the 'intent' parameter for natural-language queries but does not explicitly compare to alternatives like 'search' or 'get_mcp_server'. No when-to-use or when-not-to-use guidance is provided, leaving the agent to infer context.

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

All agent-tools (x402 + MCP + A2A directory) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Tools are mostly distinct with clear purposes. However, 'search', 'search_mcp_servers', 'search_a2a_agents', 'search_resources', and 'ask_services' have overlapping discovery functions, though descriptions differentiate them (e.g., LLM ranking vs deterministic). This could slightly confuse an agent.

Naming Consistency3/5

Naming conventions are mixed: some follow 'verb_noun' (e.g., ask_services, list_categories), some are single verbs (get, register, search, stats), and some use underscores (search_a2a_agents, search_mcp_servers). The pattern is not fully consistent but remains readable.

Tool Count5/5

11 tools is well within the recommended 3-15 range for a directory server covering x402, MCP, and A2A services. Each tool serves a distinct purpose without bloat.

Completeness4/5

The toolset covers core directory operations: discovery (multiple search variants), details, registration, safety scanning, and stats. Missing update/delete for services is a minor gap but not critical for basic usage.

Resources