Skip to main content
Glama

Arbiter x402 Market Intel

Claim the Route Pass after your transfer (free)

pass_claim
Read-onlyIdempotent

FREE. After the transfer has landed on Base, returns your ap1.… pass (claiming again returns the same pass). Then set the MCP header "Authorization: Bearer " or pass _meta["arbiter/pass"].

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": {
      "quote": "<quote>",
      "tx": "<tx>"
    },
    "name": "pass_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesThe 0x hash of the Base transaction that sent the USDC.
quoteYesThe aq1.… quote from pass_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description mostly restates the idempotency ('claiming again returns the same pass'). Its genuine added value is the post-claim credential handling — set 'Authorization: Bearer <pass>' or _meta['arbiter/pass'] — which tells the agent how to authenticate subsequent calls, plus the implicit external dependency on a landed Base transaction.

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?

Three tight sentences, front-loaded with the 'FREE.' qualifier and the timing precondition. The truncated 'ap1.…' / 'aq1.…' notation is compact but slightly opaque; otherwise 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?

With no output schema, the description carries the return-value burden and does so ('returns your ap1.… pass'), plus the credential-usage follow-up and the prerequisite. It omits failure behavior — what happens if the transfer has not landed or the tx hash is invalid.

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 coverage is 100%, with both tx and quote fully documented in the schema itself, so the baseline applies. The description adds only indirect context (that tx is a Base transfer of USDC that must have landed), not new semantics for either parameter.

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 (claim) and resource (the Route Pass), plus the return value ('returns your ap1.… pass') and the prerequisite state ('After the transfer has landed on Base'). The leading 'FREE.' distinguishes it from the paid siblings buy_route_pass_week/month without ambiguity.

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 an explicit sequencing condition: call this only after the Base transfer has landed, following a pass_quote (named in the schema). It also warns that repeat claims return the same pass, which prevents redundant retries, but it does not name alternatives such as pass_status for checking whether a pass already exists.

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