Skip to main content
Glama
Sign In

Toolbooth

by io.toolbooth
OverviewDiscussionsAdmin

x402 API discovery

x402_discover
Read-only

Search paid x402 APIs listed in Coinbase's CDP Bazaar by keyword (e.g. 'weather', 'solana token price'), optionally for one payment network and a maximum price: each result's URL, name, description, HTTP method, price per call in USD (for USDC offers), network, payTo address and its paid calls over the last 30 days. Listings are written by their sellers and aren't checked by Toolbooth. Fails (and is not charged) if the Bazaar doesn't answer. Costs $0.002 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
limitNoResults, 1–20 (default 10)
queryYesWhat the API should do, e.g. 'weather forecast' or 'web search'
networkNoPayment network: base, solana, polygon, arbitrum, ethereum, optimism, or a CAIP-2 id
maxUsdPriceNoOnly APIs costing at most this many USD per call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral facts: a $0.002 USDC per-call charge, that failures are not charged, and that listings are seller-written and unverified by Toolbooth. That trust caveat and the paid-call/result-field inventory are exactly the context annotations cannot convey.

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-loaded with the core action and only four sentences, each carrying distinct information (search semantics, result fields, trust warning, cost/failure). The first sentence is a long run-on that strings the result-field inventory together, which costs a bit of readability.

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 tool with no output schema, the description enumerates the return fields (URL, name, description, method, price, network, payTo, 30-day paid calls), discloses the per-call cost and failure billing behavior, and warns about unverified listings. Nothing an agent needs before invoking it is missing.

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 the baseline is 3, but the description adds meaning: it clarifies that network is limited to one value ('optionally for one payment network') and that maxUsdPrice is a per-call ceiling tied to the USD price reported for USDC offers. It also supplies keyword phrasings the schema's example only partly covers.

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 paid x402 APIs listed in Coinbase's CDP Bazaar') plus the discovery scope (keyword, optional network/price filters). No sibling tool in the list does API discovery, so the agent can separate it from web_search or dex_search immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete query examples ('weather', 'solana token price') and explains the two optional narrowing filters, which tells the agent when this tool fits. It stops short of naming exclusions or alternatives (e.g. when to use web_search instead), so it does not reach a 5.

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

All Toolbooth toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources