Return the current cross-chain RLUSD supply (Ethereum + XRPL) from the same PG mirror /rlusd reads. Honest-partial when either chain errored. Wrapped in the proof envelope.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It reveals key traits: 'Honest-partial when either chain errored' and 'Wrapped in the proof envelope', which go beyond a simple read-only hint. This adds useful context about error handling and output format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, each providing distinct value: purpose, error behavior, and output wrapping. No redundant or extraneous words appear, making it highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter tool without an output schema, the description covers the core functionality, error handling, and proof envelope. It does not detail the exact return format, but the essentials are present and the behavior is clear enough for an agent to understand the tool's role.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and 100% schema coverage (empty schema). Per the rubric, a baseline of 4 applies since there are no parameters for the description to explain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'current cross-chain RLUSD supply (Ethereum + XRPL)', identifying a specific verb and resource. It distinguishes this from sibling tools like get_rlusd_flow_24h by mentioning 'supply' rather than flow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The purpose is implied by the name but no guidance is provided for selection among sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource and action, from amendments and AMM pools to RLUSD supply and whale events. Even the two whale-related tools have clear boundaries: events include all events, while watchlist focuses on tagged-watchlist events. No two tools appear to overlap in purpose.
All tools follow a consistent get_<resource> pattern, with the sole exception being verify_snapshot_signature, which correctly uses a verb for a verification action. The naming is uniform, readable, and predictable throughout.
15 tools is at the upper end of the ideal range, but each tool covers a distinct aspect of the XRPL dashboard domain, from ledgers and RLUSD to RWA and UNL. The scope feels well-calibrated for a read-only dashboard server, with no redundant or trivial tools.
The tool set provides comprehensive read-only coverage of the dashboard's features, including amendment status, AMM pools, ledger stats, MPT, RLUSD supply/flow, RWA pools/families, token attestations, UNL, whale events/watchlist, and signed snapshots with verification. No obvious gaps exist for the stated purpose.
