Skip to main content
Glama

Arbiter x402 Market Intel

Benchmark an x402 seller against the whole catalog ($0.05)

seller_benchmark
Read-onlyIdempotent

For x402 sellers and builders: rank of each listing by 30-day payers, percentile in its category, price vs the category paid median, metadata gaps (input schema, output example, tags, name, description) compared with the top decile, nearest competitors, a live probe and concrete recommendations. origin = host or one paid endpoint URL. Unknown seller = error, not charged. PAID: $0.05 per call, no account. Pay with x402 over MCP (USDC on Base), or with a Route Pass (header Authorization: Bearer ap1...). 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/seller.

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

Input Schema

NameRequiredDescriptionDefault
originNoSeller host (api.example.com) or a full https URL of one of its paid endpoints. Default: the most-paid origin in the catalog (example)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it is a paid call at $0.05, supports x402/MCP or Route Pass authentication, returns payment terms without charging on unpaid calls, rejects bad input before payment, never charges for failed work, and errors on unknown sellers without charging. These details are exactly the kind of billing, auth, and failure semantics an agent needs before invoking a paid read-only tool.

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?

The description is dense but front-loads the returned information before payment and error details. It is longer than typical, but most sentences carry operational value for a paid benchmarking tool; a small amount of compression could still improve readability.

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?

For a one-parameter paid benchmarking tool with no output schema, the description is complete: it explains the returned metrics, pricing and payment paths, unpaid-call behavior, input validation, failure charging, unknown-seller handling, and the equivalent HTTP endpoint. Nothing material appears missing for an agent to decide whether and how to call it.

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 schema already documents the single origin parameter at 100% coverage, including its default. The description adds useful meaning by restating that origin can be a host or one paid endpoint URL and by specifying that an unknown seller produces an error and no charge.

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?

The description states a specific resource and action: it ranks each listing by 30-day payers, gives category percentile, price versus paid median, metadata gaps, nearest competitors, a live probe, and recommendations. This clearly distinguishes it from catalog-discovery siblings such as market_map or market_peek, which are not described as seller diagnostics.

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?

The audience is explicit: 'For x402 sellers and builders.' The origin parameter and error behavior clarify when the tool is applicable, but it does not explicitly name alternatives or say when not to use this tool versus other catalog tools.

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