Skip to main content
Glama

Arbiter x402 Market Intel

Which paid x402 endpoint should I call for this task? ($0.02)

route_task
Read-onlyIdempotent

Use BEFORE paying an unknown x402 endpoint for a job ("token safety check", "web search", "weather forecast", "send USDC", "scrape a page"). Returns the x402 listings that real buyers actually pay for that job, ranked by relevance x distinct payers in the last 30 days x recency x price, with the top 3 probed live right now for a valid 402 (dead, mispriced or free-but-listed endpoints are flagged), plus mostProven / bestValue / cheapestProven picks. task = a few words; optional max_price_usd, network (any|base|solana), probe, limit. No match = error, not charged. PAID: $0.02 per call, no account. Pay with x402 over MCP (USDC on Base), or with a Route Pass (header Authorization: Bearer ap1...). An unpaid call returns the payment terms and charges nothing; bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/route.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you need done, in a few words (<= 160 chars). Default "token safety check"
limitNoCandidates to return, 1-20 (default 8)
probeNoLive-probe the top 3 candidates (default true)
networkNoany (default) | base | solana
max_price_usdNoOptional price ceiling per call in USD, e.g. 0.01

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: it discloses the $0.02 price, the two auth paths (x402 USDC on Base or a Bearer Route Pass), that unpaid calls return payment terms at no charge, that bad input is rejected pre-payment, that failed work is never charged, and that no match yields an error rather than a charge. The ranking formula and live-probe/flagging behavior are also spelled out, which is exactly the context annotations cannot carry.

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?

The critical action and timing ("Use BEFORE paying") are front-loaded, followed by the return shape and then payment terms. It is dense — heavy use of parentheticals and slashes — but nearly every clause carries decision-relevant information rather than filler.

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 no output schema, the description carries the return-value burden and does so: ranked listings, top-3 live probes with dead/misaligned flags, and three named picks. Payment, error, and charging semantics are also covered, leaving nothing an agent needs before invoking it.

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 schema already documents every parameter including defaults and the network enum. The description only echoes the parameter names and adds "task = a few words," which is marginal value over the schema's own 160-char note; 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: it returns x402 listings matching a described job, ranked, with live probes and named picks (mostProven/bestValue/cheapestProven). An agent can immediately tell this is a discovery/routing lookup, not a purchase or a listing-browse tool, which distinguishes it from siblings like market_map or payment_options without needing their schemas.

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?

"Use BEFORE paying an unknown x402 endpoint" gives an explicit trigger condition, and concrete job examples ("token safety check", "web search", "send USDC") clarify the input shape. It does not, however, state when to prefer a sibling such as market_peek or market_map over this tool, leaving that routing decision 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