Skip to main content
Glama

Agent Exchange store

x402 Seller Report

kyreos_x402_seller_report
Read-only

[Kyreos, 0.05 USDC per call via x402 on Base] x402 Seller Report: health, rank, pricing and discovery status for any x402 provider. Returns JSON with 402index ranking, uptime, reliability score, route count. Input: {host: 'example.com'} Input: {"host":"store.agentexchange.work"}. HTTP: GET https://store.agentexchange.work/w/x402-seller-report?q=... 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 result.

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

Input Schema

NameRequiredDescriptionDefault
qNo{"host":"store.agentexchange.work"}
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds information annotations cannot express: a 0.05 USDC cost per call on Base, the concrete HTTP GET endpoint, and a non-obvious two-call handshake before any data is returned. It stops short of covering failure modes (what happens on an invalid or expired payment payload) or any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The price and resource are front-loaded, which is good, but the body carries waste: the price is stated twice (bracketed prefix and again in the payment sentence) and the duplicated 'Input:' examples add no distinguishable information. The text reads as a scraped endpoint notice rather than an edited definition.

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 by naming the concrete fields a caller receives, plus cost, endpoint, and the payment handshake. It is nearly complete for a simple two-parameter read tool; only error/precondition behavior on the payment step is absent.

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%, so both parameters are already documented in structured form and the baseline is 3. The description does add real semantics by explaining that x_payment is only supplied on the second call, but its handling of the q parameter is muddled — it presents 'Input: {host: ...}' twice, with two different examples and no explanation, which risks an agent treating q as an object rather than the JSON string the schema specifies.

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 states a specific resource and the exact payload: 'health, rank, pricing and discovery status for any x402 provider' returning '402index ranking, uptime, reliability score, route count'. That is concrete and an agent can tell what comes back. It does not, however, distinguish itself from the near-identically named sibling 'kyreos_seller_report', leaving the agent to guess between two apparently overlapping tools.

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 two-step payment protocol is spelled out explicitly: 'Call once without x_payment to get the x402 payment terms; call again with x_payment to get the result', which is genuine when-and-how guidance. What is missing is any exclusion or routing advice relative to the sibling seller-report tool, so alternatives remain unaddressed.

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