Skip to main content
Glama

Settled

by tools.settled
OverviewDiscussionsAdmin

Report whether a paid call worked

settled_report
Idempotent

Free. After paying an x402 endpoint on Base, tell Settled whether you got what you paid for. Use when: your agent has just made a real USDC payment and has the transaction hash. Not for: endpoints you did not pay, or payments on other chains. Flow: call without signature to get message_to_sign; sign it with the paying wallet (EIP-191 personal_sign); call again with signature. One report per payment, one vote per wallet per endpoint; Settled keeps only per-endpoint tallies.

Input Schema

NameRequiredDescriptionDefault
okYestrue if the call delivered what you paid for, false if it did not
txYesTransaction hash of your USDC payment to that endpoint on Base, from the last 30 days: 0x followed by 64 hex characters, e.g. 0x3f9a...c21e
urlYesThe x402 endpoint you paid
signatureNoEIP-191 personal_sign of message_to_sign by the wallet that paid (0x + 130 hex characters); omit on the first call to get message_to_sign

Output Schema

NameRequiredDescriptionDefault
okNoYour verdict, as recorded
urlNoThe endpoint
errorNosignature_required when no signature was given (sign message_to_sign and call again), or why the report was refused
paid_atNoWhen your payment was made
privacyNoWhat Settled keeps about you
reportsNoThis endpoint's report tallies
acceptedNotrue once the report is recorded
paid_usdNoWhat your transaction paid the endpoint, in USD
attestationNoEIP-191 signature over the answer; verify it with settled_verify or any EVM library
attested_atNoWhen Settled signed this answer (ISO 8601)
message_to_signNoThe exact message to sign with the paying wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / signature / description
      Previous value: -"EIP-191 personal_sign of the exact report message by the wallet that paid; omit it to get message_to_sign"New value: +"EIP-191 personal_sign of message_to_sign by the wallet that paid (0x + 130 hex characters); omit on the first call to get message_to_sign"
    • addedInput schema / properties / signature / pattern
      Added value: +"^0x[0-9a-fA-F]{130}$"
    • changedInput schema / properties / tx / description
      Previous value: -"Transaction hash (0x...) of your USDC payment to that endpoint on Base, from the last 30 days"New value: +"Transaction hash of your USDC payment to that endpoint on Base, from the last 30 days: 0x followed by 64 hex characters, e.g. 0x3f9a...c21e"
    • addedInput schema / properties / tx / pattern
      Added value: +"^0x[0-9a-fA-F]{64}$"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare a non-read-only, idempotent, non-destructive write; the description adds substantial context beyond that: the tool is free, requires an EIP-191 signature from the paying wallet, has rate/consistency limits (one report per payment, one vote per wallet per endpoint), and retains only per-endpoint tallies. These are real behavioral facts the annotations do not convey.

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-loads 'Free', then separates Use-when, Not-for, and Flow into scannable clauses with no filler. Every sentence carries actionable 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?

For a two-phase signed write with an output schema present, the description supplies the when/when-not, the signing flow, and the retention/rate constraints an agent needs. Return values are covered by the output schema, so no gap remains.

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%, with each field already documenting its type, pattern, and role, including the 'omit on first call' signature behavior. The description restates the same tx/url/ok/signature semantics in scenario language but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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?

The description states a precise verb and resource (report whether a paid x402 call worked) and anchors it to a concrete scenario: an agent that just made a real USDC payment on Base and holds the tx hash. It is clearly distinguishable from siblings like settled_check and settled_verify without opening any 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?

Explicit 'Use when' (just paid, has tx hash) and 'Not for' (unpaid endpoints, other chains) clauses remove ambiguity, and the two-step flow tells the agent exactly how to proceed. Nothing about selection or prerequisites 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