Skip to main content
Glama

Settled

by tools.settled
OverviewDiscussionsAdmin

Change feed

settled_events
Read-onlyIdempotent

Free: 25 calls/day per address, 300 with a payer record, no daily cap with a pass. Recent changes worth acting on: venue verdict flips, new suspected honeypots, settlement-integrity changes, newest first. Use when: your agent runs on a schedule and wants to react to what changed since last time. Not for: the full picture (settled_income_venues) or endpoint-level changes (settled_watch). Poll this instead of re-reading the scorecard.

Input Schema

NameRequiredDescriptionDefault
passNoSettled day pass token: lifts the free daily cap; or send it as the x-settled-pass header
limitNoHow many events to return, newest first, 1-200 (default 50)
payer_tokenNoA Settled payer token (x4t_…, from POST /x401/token with your payer record): the free tier then follows your wallet, 300 a day, through any gateway

Output Schema

NameRequiredDescriptionDefault
countNoNumber of events returned
errorNoPresent only when the call failed or needs another step: an error code such as pass_required, next to the fields that explain it
eventsNoChanges newest first: venue verdict flips, new suspected honeypots, settlement-integrity changes
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 list was built

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / payer_token
      Added value: +{
+  "description": "A Settled payer token (x4t_…, from POST /x401/token with your payer record): the free tier then follows your wallet, 300 a day, through any gateway",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds rate-limit and quota tiers (25/day, 300 with payer, uncapped with pass) that annotations do not carry, plus result ordering — genuine context beyond readOnly/idempotent hints. It does not disclose how far back events are retained or that there is no cursor parameter, so 'what changed since last time' implies statefulness the schema can't support.

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?

Dense but every sentence carries information: quota, payload contents, usage trigger, exclusions, and polling advice. The quota line leads, which delays the purpose statement slightly in favor of operational constraints.

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?

With annotations, full schema coverage, and an output schema, the remaining burden on the description is small and it covers usage, quotas, and alternatives. The notable omission is how much history is available and how to avoid re-processing events when polling, which matters for the scheduled-agent use case it recommends.

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 value by explaining what a pass and payer record buy in quota terms, mapping free-tier behavior to those two parameters. It says nothing extra about `limit` beyond the schema's own 1-200/default-50 documentation.

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?

Names the resource concretely and enumerates the event types returned (venue verdict flips, new honeypots, settlement-integrity changes) with ordering (newest first). An agent can tell it apart from settled_income_venues and settled_watch without opening either 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?

Uses explicit 'Use when' / 'Not for' framing and names the two alternative siblings with the conditions that select them. It also states the operational preference: poll this instead of re-reading the scorecard.

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