Skip to main content
Glama

xrpl_account_info

Summarize any XRP Ledger account in one call: XRP balance, reserve, spendable amount, trust lines like RLUSD, and the last 10 transactions on mainnet or testnet. Pay per call in XRP or RLUSD via x402.

Instructions

Summarize an XRP Ledger account: XRP balance, reserve, spendable amount, trust lines (e.g. RLUSD) and the last 10 transactions, from mainnet (default) or testnet. Price about $0.002. Paid per call with x402 from your XRPL_SEED wallet (XRP or RLUSD, capped by MAX_*PER_CALL and SESSION_BUDGET*). Without a wallet it returns the price quote and charges nothing. Failed calls are not charged.

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": {
      "address": "<address>"
    },
    "name": "xrpl_account_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoAsset to pay with on the XRP Ledger: XRP (default) or RLUSD
addressYesClassic XRPL r-address
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses approximate price (~$0.002), the x402 payment mechanism, budget caps (MAX_*_PER_CALL, SESSION_BUDGET_*), that a missing wallet yields a price quote with no charge, and that failures are not billed. It does not mention rate limits or whether the call is strictly read-only, keeping it below a 5.

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?

Purpose and scope are front-loaded in the first clause, with pricing and payment mechanics following. Dense but every sentence carries operational information; no filler.

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 three-parameter read tool with no output schema and no annotations, the description covers purpose, returned fields, network default, and the full cost/charging model. Only return-shape specifics (e.g., currency formatting, pagination of the 10 transactions) are absent, which is minor.

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 67%; the description adds the mainnet default for the network parameter, which the bare enum lacks, and ties XRP/RLUSD to the payment asset. The address parameter's meaning (classic r-address) is left entirely to the schema, so the description adds only modest value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Summarize an XRP Ledger account") and enumerates the returned content: XRP balance, reserve, spendable amount, trust lines, and last 10 transactions, plus network scope. It does not differentiate itself from the generic sibling call_paid_service, which could plausibly also reach paid XRPL endpoints, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Default network (mainnet) and the no-wallet fallback are stated, and the charge behavior on failure is clarified. However, there is no explicit guidance on when to prefer this tool over call_paid_service or other siblings, and no stated prerequisites beyond owning an XRPL_SEED wallet.

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