Skip to main content
Glama

Agent market (x402)

On-chain seller report for an x402 host

kyreos_seller_report
Read-only

[Kyreos, 0.05 USDC per call via x402 on Base] On-chain seller report for one x402 seller host: payers, usd, last_settlement and category from the live sellers-index.json (Base USDC Transfer logs, regenerated hourly), the same data as GET https://store.agentexchange.work/gw/bazaar/seller//report.json, plus that full report. Input: host (a hostname such as example.workers.dev). Call once without x_payment to get the x402 payment terms (0.05 USDC); call again with x_payment (the signed x402 payment) to get the report. Settles only when the report answers.

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": {
      "host": "<host>"
    },
    "name": "kyreos_seller_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesthe seller hostname, for example example.workers.dev (no scheme, no path)
x_paymentNobase64 x402 payment payload for the terms returned on the first call (0.05 USDC on Base)

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?

Adds substantial detail beyond the readOnlyHint/openWorldHint annotations: pricing, the x402 payment handshake, data freshness ('regenerated hourly'), and the settlement condition 'Settles only when the report answers'. One caveat is that it does not say what happens if the payment does not settle or the report fails (refund, error shape).

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 the pricing tag and purpose, then the data source, inputs, and payment flow in a logical order. It is dense but every clause carries information; the only mild redundancy is repeating the 0.05 USDC price in both the tag and the payment-terms sentence.

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, so the description must carry the return shape, and it does by listing the report fields and noting it also returns the full report. Payment terms, freshness, and input format are all covered, so an agent has everything needed to call it correctly.

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 description coverage is already 100%, so the baseline is 3, but the description earns extra credit by explaining the sequencing relationship between the two parameters: x_payment is the signed payload for terms obtained on the first call. It also reinforces that host is a bare hostname with no scheme or path.

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 resource and scope: 'On-chain seller report for one x402 seller host', and enumerates the returned fields (payers, usd, last_settlement, category). It also names the exact upstream data source and mirror URL, so an agent can tell this is a per-host indexed report rather than a raw chain read like chain_event_logs.

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 two-step invocation protocol: call once without x_payment for the 0.05 USDC terms, then call again with x_payment to receive the report. What it does not do is exclude any scenario or point to a sibling alternative, so it falls just short of the top band.

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