Skip to main content
Glama

Claim your endpoints (sellers)

settled_claim
Idempotent

Free. For sellers: claim every x402 endpoint paid to your wallet with one signature, on every host, so your name, website, contact and docs show next to them (plus a 10-day Seller Watch trial). Use when: you operate x402 endpoints. Not for: buyers or third parties; only the payTo wallet can sign. Flow: call with wallet and profile to get message_to_sign and issued_at; sign with that wallet; call again with issued_at and signature. action=remove withdraws a claim (reversible by claiming again). Claims never change scores.

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": {
      "wallet": "<wallet>"
    },
    "name": "settled_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
docsNoYour API documentation, as a full https URL
nameNoSeller name to show on your endpoints, up to 80 characters, e.g. Acme Data
actionNoclaim (default) or remove to withdraw an existing claim
walletYesThe payTo wallet your endpoints are paid to: 0x + 40 hex characters on Base, or a base58 address on Solana
contactNoWhere Seller Watch alerts go, strongly recommended: an email address (hello@example.com), or an https URL that receives each alert as a signed JSON POST (a webhook). Without one, alerts reach you only through the feed, your access log and answers to your own agent
websiteNoYour website, as a full https URL
issued_atNoThe issued_at timestamp returned by the first call; send it back unchanged with the signature
signatureNoSignature of message_to_sign by the wallet: EIP-191 personal_sign (0x hex) on Base, ed25519 (base58) on Solana; omit on the first call

Output Schema

NameRequiredDescriptionDefault
noteNoWhat the claim does
badgeNoOnce claimed: the next step. The seller badge and up to 10 endpoint badges with markdown and html snippets filled in, to paste where buyers look
errorNosignature_required on the first call (sign message_to_sign and call again), or why the claim was refused
coversNoThe endpoints and hosts the claim covers
walletNoThe wallet
claimedNotrue once the claim is recorded
networkNoThe wallet's network
profileNoThe published profile: name, website, contact, docs
removedNotrue once a claim is withdrawn
issued_atNoTimestamp to send back with the signature
attestationNoEIP-191 signature over the answer; verify it with settled_verify or any EVM library
attested_atNoWhen Settled signed this answer (ISO 8601)
would_coverNoThe endpoints and hosts the claim would cover
message_to_signNoThe exact message to sign with the wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / badge
      Added value: +{
      +  "description": "Once claimed: the next step. The seller badge and up to 10 endpoint badges with markdown and html snippets filled in, to paste where buyers look"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / contact / description
      Previous value: -"How buyers can reach you, e.g. hello@example.com or @handle on X"New value: +"Where Seller Watch alerts go, strongly recommended: an email address (hello@example.com), or an https URL that receives each alert as a signed JSON POST (a webhook). Without one, alerts reach you only through the feed, your access log and answers to your own agent"
    • changedInput schema / properties / contact / maxLength
      Previous value: -120New value: +200
  3. Changed13 schema fields changed
    • changedInput schema / properties / contact / description
      Previous value: -"How buyers can reach you, e.g. an email address or X handle"New value: +"How buyers can reach you, e.g. hello@example.com or @handle on X"
    • addedInput schema / properties / contact / maxLength
      Added value: +120
    • changedInput schema / properties / docs / description
      Previous value: -"URL of your API documentation"New value: +"Your API documentation, as a full https URL"
    • addedInput schema / properties / docs / format
      Added value: +"uri"
    • changedInput schema / properties / issued_at / description
      Previous value: -"The issued_at returned by the first call; send it back with the signature"New value: +"The issued_at timestamp returned by the first call; send it back unchanged with the signature"
    • changedInput schema / properties / name / description
      Previous value: -"Seller name to show on your endpoints"New value: +"Seller name to show on your endpoints, up to 80 characters, e.g. Acme Data"
    • addedInput schema / properties / name / maxLength
      Added value: +80
    • changedInput schema / properties / signature / description
      Previous value: -"Signature of message_to_sign by the wallet: EIP-191 personal_sign on Base, ed25519 on Solana"New value: +"Signature of message_to_sign by the wallet: EIP-191 personal_sign (0x hex) on Base, ed25519 (base58) on Solana; omit on the first call"
    • changedInput schema / properties / wallet / description
      Previous value: -"The payTo wallet your endpoints are paid to (0x... on Base, base58 on Solana)"New value: +"The payTo wallet your endpoints are paid to: 0x + 40 hex characters on Base, or a base58 address on Solana"
    • addedInput schema / properties / wallet / maxLength
      Added value: +64
    • addedInput schema / properties / wallet / minLength
      Added value: +32
    • changedInput schema / properties / website / description
      Previous value: -"Your website URL"New value: +"Your website, as a full https URL"
    • addedInput schema / properties / website / format
      Added value: +"uri"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the two-call sign-and-resubmit handshake, states that remove is reversible by re-claiming, clarifies claims never affect scores, and notes the free tier and trial. The auth prerequisite (payTo wallet signature) is exactly the kind of context annotations cannot carry.

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

Conciseness4/5

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

Front-loaded with purpose, then labeled Use when / Not for / Flow segments that are easy to scan. Slightly dense, and the trial parenthetical is promotional rather than operative, but no sentence is redundant.

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 values need not be explained; the description instead supplies the multi-step workflow, reversibility, and side-effect scope that an agent needs to invoke this correctly on the first attempt.

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?

With 100% schema coverage the baseline is 3, but the description adds the sequencing semantics the schema cannot express: the first call yields message_to_sign and issued_at, the second sends issued_at back with the signature, and action=remove withdraws. It does not clarify the profile fields, but the schema already documents those in detail.

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 ("claim every x402 endpoint paid to your wallet") plus scope ("on every host") and audience (sellers), which separates it from read-only siblings like settled_find_endpoints or settled_watch.

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 explicit "Use when" and "Not for" clauses, names the eligibility constraint (only the payTo wallet can sign), and routes the agent away from buyer/third-party use cases. No inference is required.

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