Skip to main content
Glama

Seller reputation by payTo address

settled_seller_reputation
Read-onlyIdempotent

Pass required. Everything Settled knows about one payTo address: the endpoints it is paid for, live/dead counts, price range, clone-farm and quote-only flags, on-chain settlements and unique payers. Use when: several endpoints share a seller and you want to judge the seller rather than one URL, or a payTo looks unfamiliar. Not for: a single endpoint’s status (settled_check). Input is the wallet address from a 402 quote.

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": {
      "address": "<address>"
    },
    "name": "settled_seller_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoSettled day pass token, if you did not send it as the x-settled-pass header
addressYesThe payTo address from a 402 quote: 0x followed by 40 hex characters (Base)
payer_tokenNoOptional. A Settled payer token (x4t_…) for your own wallet: when it is this claimed wallet, the answer carries seller_alerts, your Seller Watch alerts

Output Schema

NameRequiredDescriptionDefault
deadNoHow many are dead
liveNoHow many are live
claimNoThe seller's claim and profile, if claimed
errorNoPresent only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it
flagsNoSeller flags such as clone_farm or quote_only
hostsNoHosts serving them
addressNoThe payTo address
onchainNoOn-chain settlements and unique payers
endpointsNoEndpoints paid to it
first_seenNoWhen Settled first saw one
attestationNoEIP-191 signature over the answer; verify it with settled_verify or any EVM library
attested_atNoWhen Settled signed this answer (ISO 8601)
generated_atNoWhen this answer was built
seller_alertsNoOnly when the caller's payer record is this claimed wallet: its own Seller Watch alerts
top_endpointsNoIts main endpoints
price_range_usdNoLowest and highest price
settlement_integrityNoWhether paid activity looks organic or self-generated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payer_token
      Added value: +{
      +  "description": "Optional. A Settled payer token (x4t_…) for your own wallet: when it is this claimed wallet, the answer carries seller_alerts, your Seller Watch alerts",
      +  "type": "string"
      +}
    • addedOutput schema / properties / seller_alerts
      Added value: +{
      +  "description": "Only when the caller's payer record is this claimed wallet: its own Seller Watch alerts"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"The payTo address to look up (0x... on Base)"New value: +"The payTo address from a 402 quote: 0x followed by 40 hex characters (Base)"
    • addedInput schema / properties / address / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
  3. First observed

TDQS

A4.7/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 the description adds value beyond them: a hard auth requirement ('Pass required'), the provenance of the input (address from a 402 quote), and the conditional behavior where a payer_token for the claimed wallet triggers seller_alerts. It stops short of noting rate limits or freshness of on-chain data, keeping it below a 5.

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

Conciseness5/5

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

Front-loaded with the auth constraint, then the payload, then labeled 'Use when' / 'Not for' segments. No sentence is redundant and the structure scans cleanly.

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?

Output schema covers return shape, annotations cover safety, and the description still names what the answer contains plus the seller_alerts augmentation. Nothing an agent needs to call and interpret it correctly 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 parameters are self-documenting and the baseline is 3. The description still contributes meaning: it flags that the pass is mandatory and that the address must come from a 402 quote, which tells the agent where to source the value rather than just its format.

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 (one payTo address) and enumerates the payload: endpoints paid for, live/dead counts, price range, clone-farm and quote-only flags, on-chain settlements and unique payers. It explicitly distinguishes itself from the sibling settled_check, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Uses an explicit 'Use when' clause (several endpoints share a seller; unfamiliar payTo) and a 'Not for' clause naming the alternative tool (settled_check for single-endpoint status). This is the full when/when-not/alternative triad.

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