Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

search

Read-only

Find x402 / MCP services matching an intent or filter set.

Two usage modes (agents pick whichever fits):
  A. Natural-language: `search(intent="fetch tweets for @user")`
  B. Pure browse:      `search(has_mcp=True, category="defi", top_k=10)`
     At least one of `intent`, `category`, `chain`, `has_mcp`,
     `min_confidence` must be supplied — otherwise the call is
     rejected (we won't dump 2300+ rows).

Results are ranked by:
    (health=ok AND tx_30d>0) → health=ok → has-quality-signal →
    confidence → tx_30d → recency.
So the highest-quality real-traffic services appear first.

Each item includes (when available):
  - confidence    : 0.0–1.0 x402scan quality score.
  - tx_30d        : 30-day x402 payment count (proxy for real usage).
  - match_snippet : FTS snippet showing where `intent` hit ([[token]]).
  - match_reason  : list[str] of human-readable ranking signals.
  - mcp_url       : populated when the service exposes an MCP endpoint
                    (you can call it directly via streamable-http).
Agents should prefer items with non-null confidence and tx_30d > 0
unless the user explicitly wants experimental endpoints.

Args:
    intent: What the agent wants to do (English or Chinese). Optional
        when at least one structured filter is set. Synonym expansion
        covers twitter↔X↔推特, whale↔巨鲸, price↔价格 etc.
    top_k: Max services to return (default 5, hard cap 25).
    max_price_usd: Upper bound on per-call price in USD.
    category: Filter (see `list_categories`).
    chain: "base", "polygon", "solana", "arbitrum", ...
    min_confidence: Minimum confidence (0.0–1.0). 0.8+ keeps only
        services x402scan rates as high-quality.
    has_mcp: When true, return only services with a callable MCP
        endpoint. Use this when the agent wants to chain another MCP
        server rather than perform raw HTTP+x402.

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

Input Schema

NameRequiredDescriptionDefault
chainNo"base", "polygon", "solana", "arbitrum", ...
top_kNoMax services to return (default 5, hard cap 25).
intentNoWhat the agent wants to do (English or Chinese). Optional when at least one structured filter is set. Synonym expansion covers twitter↔X↔推特, whale↔巨鲸, price↔价格 etc.
has_mcpNoWhen true, return only services with a callable MCP endpoint. Use this when the agent wants to chain another MCP server rather than perform raw HTTP+x402.
categoryNoFilter (see `list_categories`).
max_price_usdNoUpper bound on per-call price in USD.
min_confidenceNoMinimum confidence (0.0–1.0). 0.8+ keeps only services x402scan rates as high-quality.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Filter (see `list_categories`)."
    • addedInput schema / properties / chain / description
      Added value: +"\"base\", \"polygon\", \"solana\", \"arbitrum\", ..."
    • addedInput schema / properties / has_mcp / description
      Added value: +"When true, return only services with a callable MCP endpoint. Use this when the agent wants to chain another MCP server rather than perform raw HTTP+x402."
    • addedInput schema / properties / intent / description
      Added value: +"What the agent wants to do (English or Chinese). Optional when at least one structured filter is set. Synonym expansion covers twitter↔X↔推特, whale↔巨鲸, price↔价格 etc."
    • addedInput schema / properties / max_price_usd / description
      Added value: +"Upper bound on per-call price in USD."
    • addedInput schema / properties / min_confidence / description
      Added value: +"Minimum confidence (0.0–1.0). 0.8+ keeps only services x402scan rates as high-quality."
    • addedInput schema / properties / top_k / description
      Added value: +"Max services to return (default 5, hard cap 25)."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds substantial context beyond them: the rejection behavior for empty filters, the full ranking precedence, the hard cap of 25, synonym expansion across English/Chinese, and what mcp_url enables. This tells the agent exactly how results are ordered and why a call might fail.

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 ranking block and usage modes are well front-loaded and earn their space, but the Args section duplicates the input schema's parameter descriptions almost verbatim, adding roughly a third of redundant text. Structured formatting helps, yet the description could be materially shorter without losing information.

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

Completeness5/5

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

For a read-only search over a large registry, the definition covers preconditions, ranking, result fields, and endpoint chaining. With an output schema present it does not need to explain return types further, and the result-field notes it does include (confidence, tx_30d, match_snippet) serve as interpretation rather than duplication.

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 most of the Args section restates what is already structured. The genuine added value is cross-parameter validation (at least one filter required) and interpretive guidance on min_confidence (0.8+ = high quality) and has_mcp (chaining another MCP server vs raw HTTP+x402), which the schema does not express.

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?

Opens with a specific verb+resource ('Find x402 / MCP services matching an intent or filter set') and immediately enumerates the two calling modes. It is distinguishable from search_a2a_agents and search_resources by naming the x402/MCP service domain, but it never explicitly contrasts itself with the closest sibling, search_mcp_servers, so an agent must infer the boundary.

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?

Gives concrete when-to-use modes with worked call examples (natural-language vs pure browse), states a hard precondition ('at least one of intent, category, chain, has_mcp, min_confidence must be supplied — otherwise the call is rejected'), and adds decision guidance ('prefer items with non-null confidence and tx_30d > 0 unless the user explicitly wants experimental endpoints'). It also routes the agent to list_categories for valid filter values.

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.