Skip to main content
Glama

Arbiter x402 Market Intel

Buy a Route Pass with a plain USDC transfer: get a quote (free)

pass_quote
Read-only

FREE, no x402 needed. Returns a quote and the USDC amount to send on Base to this service. After sending, call pass_claim with the quote and the transaction hash to receive the pass token.

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

Input Schema

NameRequiredDescriptionDefault
fromNoOptional: the Base address you will pay from (0x + 40 hex). With it you pay a round amount; without it you must send the exact odd amount quoted.
planNoweek = 7 days, up to 300 calls, $1; month = 30 days, up to 1,500 calls, $3. Default week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally; the description usefully adds that the call itself is free and requires no x402 payment. It omits the practically important behavior of quote lifetime/expiry and whether a quote can be reused, which matters for a non-idempotent quote issued ahead of an on-chain transfer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the cost/eligibility fact ('FREE, no x402 needed'), followed immediately by the return value and next step. No filler or restated title.

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?

With no output schema, the description carries the burden of describing returns and does so at a high level (a quote plus the USDC amount to send). For a free, two-optional-parameter read tool this is close to sufficient; only the quote's structure and validity window are left unstated.

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%, and the schema already explains both parameters in detail, including the round-amount versus exact-odd-amount consequence of supplying `from`. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 states a specific verb and resource ('Returns a quote and the USDC amount to send on Base') and clarifies the cost model ('FREE, no x402 needed'), which meaningfully separates it from the paid purchase siblings. It does not name buy_route_pass_month or buy_route_pass_week, so an agent must infer on its own when this quote flow beats those alternatives.

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 explicit sequencing: get the quote here, send USDC, then call pass_claim with the quote and transaction hash. It also frames the condition that selects this path (free, no x402 handshake). It stops short of stating when to prefer the dedicated week/month purchase tools or what to do if a quote expires.

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