Asteroid XRPL Hub

Get ASTEROID project-declared treasury escrows

get_escrow_stats

Read-onlyIdempotent

Deprecated — use get_escrow_schedule, which is enveloped and adds per-escrow locked/releasable/expired state. Time-locked project-declared treasury ASTEROID escrows on the XRP Ledger: every escrow with its amount, finish-after (unlock) date, cancel-after date, plus the total escrowed amount and its share of supply. The treasury role is an owner-confirmed declaration; the escrow objects themselves are ledger-readable. Escrow existence does not establish who controls the destination account after release.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_escrow_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the read-only safety profile is covered. The description adds genuinely useful caveats beyond the schema: the treasury role is an owner-confirmed declaration, not a verified fact, and escrow existence does not establish who controls the destination account. That interpretive framing is real added value, though it stops short of describing pagination or output shape.

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?

The deprecation notice and alternative are front-loaded in the first clause, which is the most important routing information. Subsequent sentences are dense but each carries content (scope, caveats). Slightly long, but no 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?

With no output schema, the description carries the burden of describing returns and does so field-by-field (amount, unlock date, cancel date, total escrowed, share of supply). Combined with the deprecation routing and the control caveat, an agent has everything needed to decide and call correctly.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description instead specifies the returned field semantics, which is appropriate.

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 resource and scope: time-locked project-declared treasury ASTEROID escrows on the XRP Ledger, with the exact fields returned (amount, finish-after, cancel-after, totals, share of supply). It also names the sibling get_escrow_schedule and how it differs, so an agent can distinguish the two without opening schemas.

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?

Explicitly marks itself deprecated and routes the agent to get_escrow_schedule, explaining that the successor adds per-escrow locked/releasable/expired state. This is a clear when-not-this-tool plus a named alternative, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asteroid XRPL Hub tools Inspect

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

Need Help?