Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

search_resources

Read-only

Unified search across x402 services, MCP servers and A2A agents.

Args:
    intent: Natural-language query.
    protocol: Optional filter: "x402", "mcp" or "a2a".
    top_k: Max resources to return (1-50).

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

Input Schema

NameRequiredDescriptionDefault
top_kNoMax resources to return (1-50).
intentNoNatural-language query.
protocolNoOptional filter: "x402", "mcp" or "a2a".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / intent / description
      Added value: +"Natural-language query."
    • addedInput schema / properties / protocol / description
      Added value: +"Optional filter: \"x402\", \"mcp\" or \"a2a\"."
    • addedInput schema / properties / top_k / description
      Added value: +"Max resources to return (1-50)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the description need not repeat it. The description adds essentially no behavioral context beyond the annotations — no ranking/relevance behavior, no indication of what happens when intent is null (which is a realistic and ambiguous call given all parameters are optional), and no note on result ordering.

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 lead sentence is well front-loaded and precise. However, the three-line Args block duplicates the schema descriptions word-for-word and earns no place; removing it would lose nothing and make the definition tighter.

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 low-complexity, annotation-covered, output-schema-backed search tool with 0 required parameters, the description is close to sufficient: purpose and filters are clear. The remaining gap is disambiguation from the several search_* siblings, which matters given this is one of three search tools in the same namespace.

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 Args block is a verbatim restatement of the schema and adds zero marginal meaning. The one genuinely useful semantic — what a null/omitted intent means (browse-all vs error) — is absent from both schema and description.

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 first sentence states a specific verb and resource ("Unified search across x402 services, MCP servers and A2A agents"). The word "unified" implicitly contrasts it with the protocol-specific siblings search_mcp_servers and search_a2a_agents, so an agent can reasonably place it, though no sibling is named 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?

Usage is only implied: 'unified' suggests using this when you want cross-protocol coverage. Nothing states when to prefer search_mcp_servers or search_a2a_agents instead, or whether this tool federates/aggregates those results. There are no exclusions or prerequisites.

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.