Skip to main content
Glama

Arbiter x402 Market Intel

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Prices, the receiving address, the x402-over-MCP retry format, and how to use a Route Pass instead (bought once with x402 or with a plain USDC transfer on Base, no x402 client needed).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's real addition is cost behavior: the call is free and requires no x402 client, and it explains that a Route Pass can be acquired via plain USDC transfer on Base. It says nothing about rate limits, response shape, or freshness of the quoted prices, which matters since there is no output schema.

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?

A single sentence with the key qualifier 'FREE.' front-loaded, and no filler. It is dense with protocol jargon ('x402-over-MCP retry format') that could slow an unfamiliar agent, but every clause carries information.

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, read-only informational tool with no output schema, the description lists the payload contents well enough that an agent knows what it will get back. A brief note on whether prices are live or indicative would close the remaining gap.

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 disambiguate and the baseline of 4 applies. The schema's additionalProperties=false also makes the no-argument contract unambiguous.

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 enumerates exactly what the tool surfaces: prices, receiving address, the x402-over-MCP retry format, and the Route Pass alternative. That is more specific than the title, and it implicitly separates this documentation endpoint from the transactional siblings (buy_route_pass_week/month, pass_quote). It stops short of an explicit verb like 'returns' or 'describes', so it is clear but not perfectly framed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opening with 'FREE.' tells an agent this call costs nothing, which is meaningful guidance in a payment-oriented toolset, and mentioning Route Pass implies where to go next. However, it never states when to call this versus pass_quote or buy_route_pass_month, and it gives no prerequisite or sequencing advice. Usage is implied rather than directed.

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