Skip to main content
Glama

Pre-spend check (pay / caution / avoid)

settled_preflight
Read-onlyIdempotent

Pass required. The call to make right before paying an unfamiliar x402 endpoint: a fresh probe, parsed quote, payability, payTo on-chain history, seller integrity, the scout’s real-payment delivery result and a honeypot scan, as one signed answer with a recommendation (pay, caution or avoid) and reasons. Use when: real money is about to leave your wallet and settled_check was stale or not enough. Not for: browsing (settled_find_endpoints) or endpoints you already verified. After: compare pay_to and price with the 402 you receive, pay, then call settled_report.

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": {
      "url": "<url>"
    },
    "name": "settled_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL of the x402 endpoint, e.g. https://api.example.com/search
passNoSettled day pass token, if you did not send it as the x-settled-pass header
forceNotrue to probe the endpoint now instead of reusing a result up to 5 minutes old
payer_tokenNoOptional. A Settled payer token (x4t_…) for your own wallet: when that wallet is the endpoint's claimed seller, the answer carries seller_alerts, your Seller Watch alerts

Output Schema

NameRequiredDescriptionDefault
urlNoThe endpoint
errorNoPresent only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it
flagsNoRisk flags
payeeNoWhether the payTo exists on-chain, and the seller's other endpoints and settlement integrity
quoteNoThe parsed 402 quote Settled sees: network, asset, price_usd, pay_to
cachedNoWhether the probe came from Settled's 5-minute cache
onchainNoSettlements and unique payers over the last 30 days
qualityNoQuality score breakdown
reasonsNoWhy, in plain words
reportsNoPaying agents' reports
deliveryNoThe scout's last real purchase and whether it matched the listing
honeypotNoHoneypot scan of the listing text
livenessNoFresh probe results
verifierNoThe verdict in the x402 Foundation Domain Discovery working group’s draft verifier schema: verdict (true|false|inconclusive), a reason code from its closed set, evidence (none|terms|probe|purchase; purchase_by verifier when Settled bought), the quote’s digest, and an attestation with the key URL, a signed record URL, the two domains compared, valid_until and the relationship disclosure; method_digest pins the method document (/verifier-method.md)
checked_atNoWhen this check ran
payabilityNoPayability verdict and the verb that pays
attestationNoEIP-191 signature over the answer; verify it with settled_verify or any EVM library
attested_atNoWhen Settled signed this answer (ISO 8601)
descriptionNoThe listing's description
seller_claimNoThe seller's claim and profile, if claimed
seller_alertsNoOnly when the caller's payer record is the claimed wallet: that seller's own Seller Watch alerts (down_now, new_24h, latest, feed)
recommendationNopay, caution or avoid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / verifier
      Added value: +{
      +  "description": "The verdict in the x402 Foundation Domain Discovery working group’s draft verifier schema: verdict (true|false|inconclusive), a reason code from its closed set, evidence (none|terms|probe|purchase; purchase_by verifier when Settled bought), the quote’s digest, and an attestation with the key URL, a signed record URL, the two domains compared, valid_until and the relationship disclosure; method_digest pins the method document (/verifier-method.md)"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / payer_token
      Added value: +{
      +  "description": "Optional. A Settled payer token (x4t_…) for your own wallet: when that wallet is the endpoint's claimed seller, 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 the claimed wallet: that seller's own Seller Watch alerts (down_now, new_24h, latest, feed)"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds what the annotations cannot: that a pass is required, that the result is a *signed* answer with a pay/caution/avoid verdict plus reasons, and that a cached result up to 5 minutes old may be reused (with force to bypass). It stops short of saying what a stale-pass or probe-failure response looks like, which is the main residual gap.

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 the authorization requirement and the purpose, then structured into Use when / Not for / After. It is a long single-sentence inventory of capabilities that borders on a run-on, but nearly every clause carries routing or behavioral information.

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?

For a multi-signal, payment-gating tool the description gives the full decision context: what is aggregated, what verdict comes back, when to reach for it, what to do afterward, and that the pass is mandatory. With an output schema present it need not describe return fields; only failure/degraded-probe behavior and the meaning of the verdicts are left implicit.

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% and every parameter (url, pass, force, payer_token) already carries its own description, so the schema does the heavy lifting. The description only adds the header alternative for pass ('Pass required') and the notion of a fresh probe; it says nothing about payer_token or force beyond what the schema states. 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?

States a specific verb and resource ('the call to make right before paying an unfamiliar x402 endpoint') and enumerates exactly what the tool aggregates: fresh probe, parsed quote, payability, payTo on-chain history, seller integrity, scout delivery, honeypot scan. This is clearly distinguishable from settled_check, settled_find_endpoints and settled_seller_reputation 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?

Contains explicit 'Use when' (real money about to leave the wallet; settled_check was stale or not enough), 'Not for' (browsing -> settled_find_endpoints; already-verified endpoints), and an 'After' sequence (compare pay_to/price with the 402, pay, then settled_report). The alternatives are named with the condition that selects them.

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