Skip to main content
Glama

Settled

by tools.settled
OverviewDiscussionsAdmin

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.

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)

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
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
    • 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}$"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, but the description still adds valuable operational context: 'Pass required' flags the auth prerequisite and the field list tells the agent what evidence the judgment rests on. It stops short of describing freshness or rate limits, so not a full 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?

Three tight sentences, front-loaded with the payload summary then the when/when-not routing, with zero filler. Every clause carries selection-relevant information.

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?

An output schema exists, so return-value documentation is unnecessary, and the description covers selection, auth prerequisite, and input provenance. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100% and the schema already states the 0x+40-hex format and the 402-quote provenance, so the description largely restates what is structured. 'Pass required' and 'Input is the wallet address from a 402 quote' add workflow context but no new syntax or semantics beyond the schema.

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 verb and resource ('Everything Settled knows about one payTo address') and enumerates exactly what is returned: endpoints, live/dead counts, price range, clone-farm and quote-only flags, settlements, unique payers. This is clearly distinguishable from settled_check, which it names as the single-endpoint alternative.

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?

Explicit when-to-use ('several endpoints share a seller', 'a payTo looks unfamiliar') and explicit when-not ('Not for: a single endpoint's status') with the named alternative (settled_check). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Settled toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources