Skip to main content
Glama

Agent Exchange router

Check an x402 seller (host)

check_seller
Read-only

Everything the census knows about one host: resources listed, how many answer a valid 402, dead listings, verdict (live | partial | dead | unverified), price range, catalogs, discovery files present (/.well-known/x402, agent card, llms.txt, openapi.json) and the on-chain settlement facts for its payTo addresses (distinct payers, payments, USDC volume, first/last payment, sampler share) or 'unresolved'.

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

Input Schema

NameRequiredDescriptionDefault
hostYeshost name, e.g. api.example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuine behavioral context beyond that — the verdict taxonomy (live | partial | dead | unverified), the fact that dead listings and 402-answering counts are computed, and that settlement facts can come back as 'unresolved'. It still says nothing about behavior for an unknown host (empty result vs error) or about latency/caching.

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?

It is a single run-on sentence that spends its length on a field inventory; the scoping idea is front-loaded, but the parenthetical verdict list and nested settlement enumeration make it dense and harder to scan than a short lead plus a field summary. Little of it is wasted, but the structure is a dump rather than a structured brief.

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 correctly carries the return-value burden and names nearly every field an agent would receive, including the payoff data (verdict, price range, settlement stats) and the 'unresolved' edge case. What's missing is input robustness and the behavior on a host the census has never seen, which matters for a lookup tool.

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% with one required string already documented as 'host name, e.g. api.example.com'. The description adds no meaning beyond that — no note on whether to include a scheme, port, or subdomain handling, and no guidance on canonicalization. Baseline 3 applies since the schema does the work.

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?

States a specific resource and retrieval intent: 'Everything the census knows about one host,' then enumerates exactly what that bundle contains (listings, 402 responses, verdict, price range, discovery files, settlement facts). The verb is implicit (retrieve/lookup) rather than explicit, and it never names a sibling, so the agent must rely on the 'one host' scoping to distinguish it from resource-level tools.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says to prefer this over resource-level lookups or catalog search, and no preconditions (e.g., host not in census, scheme/port format, rate limits) are stated. The only usable signal is the implicit scope 'one host,' which an agent must infer.

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