Skip to main content
Glama

Arbiter x402 Market Intel

Buy a 30-day Route Pass ($3, up to 1,500 calls) ($3.00)

buy_route_pass_month
Read-only

One x402 payment of $3 returns a pass token that unlocks route_task, seller_benchmark and market_map for 30 days (up to 1,500 successful calls). Then set the MCP client header "Authorization: Bearer " or pass _meta["arbiter/pass"]. PAID: $3.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/month.

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_month"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior2/5

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

The description itself is unusually transparent about behavior: a $3.00 charge, no account required, USDC on Base, no charge on unpaid calls, rejection before payment on bad input, no charge for failed work. However, that directly conflicts with the annotation readOnlyHint=true and idempotentHint=false framing — a tool that spends money and issues a token is not a read-only operation, so an agent auto-approving on the annotation would be misled. The disclosure is strong but conflicts with the structured safety signal.

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 offer and price, then the post-purchase setup step, then payment/failure terms — a logical order. It is dense but every sentence carries information; "Same data as GET /v1/pass/month" is the only marginal sentence and is cheap.

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?

Covers cost, what is unlocked, duration and call cap, how to present the token afterward, and what happens on unpaid/failed calls — enough for a zero-parameter purchase tool with no output schema. Minor gaps remain: token lifetime vs. the 1,500-call cap, renewal behavior, and where the x402 wallet/payment flow is negotiated.

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 there is nothing for the description to compensate for; the empty schema is self-evident. It usefully describes the invocation mechanics that are not parameters but still matter at call time (the pass header and the _meta key), which adds value beyond the schema.

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+resource+scope: "One x402 payment of $3 returns a pass token" unlocking route_task, seller_benchmark and market_map for 30 days / 1,500 calls. The 30-day term and price distinguish it cleanly from buy_route_pass_week, and the title's "up to 1,500 calls" bounds the entitlement.

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 clear operational context: buy this when you need to unlock the three paid route tools, then set the Authorization bearer header or _meta["arbiter/pass"]. It does not name the alternatives it supersedes (buy_route_pass_week, pass_quote, pass_status) or say when a week pass or quote-first flow is preferable, so exclusion guidance is missing.

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