Skip to main content
Glama

Agent Exchange router

Find x402 resources

find_resources
Read-only

Search the Agent Exchange x402 census (every resource listed in the CDP Bazaar and PayAI catalogs, probed unpaid). Returns ranked resources with URL, method, price in USD, network, our probe verdict (live = answered a valid 402 today), on-chain payers and settled USD for the seller's payTo, catalogs it appears in, and links to https://bazaar.agentexchange.work/r/. Filter by network (base, solana, base-sepolia, polygon...), max_price_usd, status (live|dead|any).

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

Input Schema

NameRequiredDescriptionDefault
limitNodefault 20
queryYeswords, a host name, or a URL fragment
statusNodefault any
networkNobase | base-sepolia | solana | polygon | arbitrum | xlayer | other
max_price_usdNoonly resources priced at or below this many USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description goes well beyond that: it explains that listings are probed unpaid, defines the probe verdict ('live = answered a valid 402 today'), and enumerates what comes back (payers, settled USD, catalog membership, deep links). That is meaningful behavioral context an agent cannot get from the annotations or schema.

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?

Two sentences, front-loaded with purpose before the return-field enumeration, with no filler. The long parenthetical and comma-spliced field list make it dense, but every clause carries useful information rather than restating the name.

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?

With five parameters and no output schema, the description correctly compensates by enumerating the returned fields and explaining the verdict semantics and link format. Nothing essential for calling or interpreting results is missing.

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%, so the schema already documents query, limit, status, network, and max_price_usd. The description adds only the enumerated network examples and the definition of 'live' relevant to the status filter, largely echoing what the schema already provides; baseline 3 is appropriate.

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 description names a specific verb and resource ('Search the Agent Exchange x402 census') and scopes it precisely to resources from the CDP Bazaar and PayAI catalogs, probed unpaid. That narrows it against siblings like search_all_catalogs, but it never explicitly states how it differs from that sibling, so the differentiation is implied rather than declared.

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?

It lists the available filters (network, max_price_usd, status) and defines what 'live' means, which conveys how to narrow a search. However, there is no guidance on when this tool should be preferred over siblings such as search_all_catalogs, resource, or census_stats, and no exclusions or prerequisites are stated.

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