Skip to main content
Glama

Search x402 services

search_x402_services
Read-onlyIdempotent

Search verified x402 sellers by capability (from Agenstry, Open 402, pay.sh, the Official MCP Registry, apis.io and other public registries; each with price, networks and evidence of a live 402 or manifest). Free tier returns the top 5; full results are the paid /search endpoint (x402 or MPP) on this host. Calls and paying wallets are P0's own on-chain transfer counts, null where not measured. Not for picking one service for a concrete task (use best_service_for_task), for market-wide totals (use x402_market_stats) or for this host's own products (use list_paid_data_products).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_x402_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYescapability to look for, e.g. 'web search', 'llm inference'
networkNooptional CAIP-2 filter, e.g. eip155:8453
include_testnetsNoalso list services that exist only on test networks (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds what they cannot: data provenance across multiple registries, the existence of a free tier capped at 5 results versus a paid /search endpoint, and that calls/wallets are null where unmeasured. These are real behavioral constraints that change how an agent should interpret and budget a call.

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

Conciseness4/5

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

Front-loads purpose and pushes the routing guidance into a single trailing sentence, so it reads efficiently; the parenthetical registry list and the free-tier/paid-endpoint aside are long but each carries actionable information. Dense rather than 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 still conveys result contents (price, networks, 402 evidence, on-chain counts) and the free-tier truncation, which is what an agent needs to interpret a short result list. It stops short of explaining pagination or how to reach the paid endpoint, a minor gap.

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 coverage is 100% and each parameter (query, network, include_testnets) carries its own description with examples, so the description adds no parameter-level meaning beyond the schema. Baseline 3 applies.

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 (search verified x402 sellers by capability), names the registries it draws from, and enumerates the fields returned (price, networks, live-402 evidence). An agent can distinguish it from best_service_for_task and x402_market_stats from the description alone.

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?

Explicitly carves out three negative cases and names the correct sibling for each: not for picking one service (best_service_for_task), not for market totals (x402_market_stats), not for this host's own products (list_paid_data_products). Nothing is left to 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.

Resources