Skip to main content
Glama

Arbiter x402 Market Intel

Buy a 7-day Route Pass ($1, up to 300 calls) ($1.00)

buy_route_pass_week
Read-only

For agents that route many tasks: one x402 payment of $1 returns a pass token that unlocks route_task, seller_benchmark and market_map for 7 days (up to 300 successful calls; route_task lists at $0.02). Then set the MCP client header "Authorization: Bearer " or pass _meta["arbiter/pass"]. PAID: $1.00, no account. Pay with x402 over MCP (USDC on Base). 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/pass/week.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Far beyond the annotations, it discloses the payment rail (x402, USDC on Base), that no account is needed, how the resulting token is presented (Authorization: Bearer header or _meta["arbiter/pass"]), the call cap (300), and failure economics (unpaid calls return terms and charge nothing, bad input is rejected before payment, failed work is never charged). The only tension is readOnlyHint=true sitting alongside a $1 charge, but the description openly states the cost, so an agent is not misled.

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?

It is front-loaded with the value proposition and then the payment/auth mechanics, with no filler sentences. It is dense—stacked parentheticals and a trailing endpoint-parity note—so it reads more like a packed spec than a clean summary, but nothing is wasted.

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?

For a zero-parameter purchase tool with no output schema, this covers price, payment protocol, auth mechanics, caps, and error/charging semantics, with the return value (a pass token) stated. The remaining gap is guidance on the adjacent pass tools (monthly pass, quote, claim, status) that an agent would need to pick among.

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?

The tool takes zero parameters, so the schema has nothing to explain and the baseline is 4. The description adds useful operational context about the credential that subsequent calls need, without inventing parameters for this call.

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?

The description names a specific action (one x402 payment of $1 buying a pass token) and the exact scope it unlocks (route_task, seller_benchmark, market_map for 7 days, up to 300 calls). An agent can tell this apart from per-call tools and from the monthly variant without inspecting any schema.

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?

It gives an explicit targeting condition ("For agents that route many tasks") plus the break-even economics (route_task lists at $0.02 vs a $1 pass for 300 calls), which is exactly the trigger an agent needs. It does not explicitly contrast with buy_route_pass_month or point to pass_quote/pass_claim/pass_status for pre-purchase checks, so the alternative routing is only implied.

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