Skip to main content
Glama

Settled

by tools.settled
OverviewDiscussionsAdmin

Buy a Watchdog for an x402 endpoint

settled_watch

Paid: $2.00 USDC on Base over x402 inside MCP (the first call returns the payment requirements; @x402/mcp clients pay automatically). Buys 30 days of monitoring for one x402 endpoint: probed about every 15 minutes, with a signed alert whenever status, payability, price or payTo changes. Use when: your agent depends on one endpoint and must learn quickly if it changes. Not for: one-off checks (settled_check). Give url to start or watch_id to renew; give webhook to have alerts POSTed, else read them with settled_watch_alerts. Returns watch_id.

Input Schema

NameRequiredDescriptionDefault
urlNoThe x402 endpoint to watch, e.g. https://api.example.com/search; required unless watch_id is given
webhookNohttps URL that receives each alert as a signed POST; omit to poll with settled_watch_alerts
watch_idNoThe watch_id of an existing watch to renew for 30 more days; give this or url, not both

Output Schema

NameRequiredDescriptionDefault
urlNoThe watched endpoint
noteNoWhat happens next
errorNoPresent only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it
alertsNoURL of the alerts feed
manageNoURL of the watch
statusNoactive or expired
acceptsNoPresent when payment is needed: the x402 payment requirements; pay one and call again with the payment in _meta
renewedNotrue when this call renewed an existing watch
baselineNoThe endpoint's state when the watch started
deliveryNowebhook or poll
watch_idNoThe watch's id: keep it to read alerts and to renew
created_atNoWhen the watch started
expires_atNoWhen it ends unless renewed
attestationNoEIP-191 signature over the answer; verify it with settled_verify or any EVM library
attested_atNoWhen Settled signed this answer (ISO 8601)
x402VersionNoPresent when payment is needed: the x402 version of the requirements
alert_formatNoWhat an alert contains
webhook_hostNoHost the alerts are POSTed to, if a webhook was given

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / watch_id / description
      Previous value: -"The watch_id of an existing watch to renew for 10 more days; give this or url, not both"New value: +"The watch_id of an existing watch to renew for 30 more days; give this or url, not both"
  2. Changed3 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"The x402 endpoint to watch; omit it when renewing"New value: +"The x402 endpoint to watch, e.g. https://api.example.com/search; required unless watch_id is given"
    • changedInput schema / properties / watch_id / description
      Previous value: -"An existing watch to renew for 10 more days, instead of buying a new one"New value: +"The watch_id of an existing watch to renew for 10 more days; give this or url, not both"
    • changedInput schema / properties / webhook / description
      Previous value: -"Optional https URL that receives each alert as a signed POST"New value: +"https URL that receives each alert as a signed POST; omit to poll with settled_watch_alerts"
  3. 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 by disclosing the $2.00 USDC cost on Base, the x402 payment handshake on first call, 30-day duration, ~15-minute probe interval, and that alerts are signed and fire on status/payability/price/payTo changes. The non-idempotent, mutating nature is clear from 'buys 30 days' and 'renew', consistent with readOnlyHint=false.

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?

Every clause carries information and the use/not-for routing is compact. The payment preamble is dense and parenthetical, slightly delaying the core purpose statement, but nothing is filler.

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 paid, long-lived, alerting watch tool the description covers price, payment flow, duration, probe frequency, alert channel, and return value (watch_id). With annotations and an output schema present, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds decision-level semantics: url vs watch_id as mutually exclusive entry paths with renewal implications, and webhook vs polling via settled_watch_alerts. That is meaning beyond the field descriptions, though the 30-day renewal effect of watch_id is only implied.

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 action and resource: buys 30 days of monitoring for one x402 endpoint, with probe cadence and alert triggers spelled out. It also explicitly carves itself apart from settled_check, so an agent can distinguish it from siblings 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: your agent depends on one endpoint and must learn quickly if it changes' and 'Not for: one-off checks (settled_check)', naming the alternative directly. It also routes the two entry modes (url to start, watch_id to renew) and the alert delivery choice (webhook vs settled_watch_alerts).

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