Skip to main content
Glama

apex-dev

X402 price comps

x402_price_comps
Read-onlyIdempotent

Live x402 market price comparison across 38,000+ indexed Coinbase Bazaar, Circle, and Arc paid APIs: min/p25/median/p75/max USD, suggested competitive price, and top competing endpoints. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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": {
      "q": "<q>"
    },
    "name": "x402_price_comps"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCategory, task, or keywords to benchmark (e.g. pdf to markdown, defillama tvl).
limitNoOptional max comparable endpoints (1-30, default 12).
networkNoOptional network filter (e.g. Base, Solana, Arc).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description still adds material context the annotations lack: a hard cost of $0.002 per call, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the fact that a first unpaid call returns terms. It does not say what happens if payment is malformed or expired, leaving a small gap.

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 what the tool returns, followed by cost/rails, then the two-call protocol — a sensible ordering with no filler. The first sentence is dense with comma-separated data sources and percentiles, which is efficient but slightly taxing to parse in one pass.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates fully by naming the returned statistics and the competing-endpoint list. Payment mechanics, pricing, and the required two-step flow are all present, so nothing an agent needs before invoking it is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by explaining that `payment` is not a normal parameter but a second-call handshake token obtained from a terms call, which the schema's one-line 'signed x402 payment payload' does not convey. It also frames `q` as a benchmark subject, adding intent beyond the schema example.

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?

Specific verb+resource: 'Live x402 market price comparison across 38,000+ indexed Coinbase Bazaar, Circle, and Arc paid APIs.' It then enumerates the exact statistics returned (min/p25/median/p75/max USD, suggested price, top competitors), which no sibling tool covers. An agent can tell instantly this is a benchmarking tool, not a rendering or lookup tool.

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 invocation protocol: 'Call once without `payment` for terms, then call again with `payment`.' That is strong, actionable sequencing guidance an agent would otherwise have to guess. It does not state when-not to use it or name a cheaper alternative for cases where the paid call is unwanted, which keeps it below a 5.

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