Skip to main content
Glama
cryptoapis-address-latest

cryptoapis-address-latest

Official

XRP address balance and latest activity

xrp_address_latest
Read-onlyIdempotent

Query XRP address balances, transactions, and next sequence numbers on mainnet or testnet to inspect account activity and prepare transactions.

Instructions

Query latest XRP (Ripple) address data. Cursor pagination: use 'nextStartingAfter' from response as 'startingAfter'.

Actions: • get-balance: Get address XRP balance • list-transactions: Get address transactions • get-next-sequence: Get next available sequence number for transactions

Networks: mainnet, testnet

Credits by action (source: OpenAPI): • get-balance: xrp 20 • get-next-sequence: xrp 20 • list-transactions: xrp 110

Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.

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": {
      "action": "<action>",
      "network": "<network>",
      "address": "<address>"
    },
    "name": "xrp_address_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return (max 50)
actionYesAction to perform: get-balance, list-transactions, get-next-sequence
addressYesXRP address to query
contextNoOptional context for the request - echoed back in response
networkYesNetwork name: mainnet or testnet
sortingOrderNoSort order: ascending (oldest first) or descending (newest first)
startingAfterNoPagination cursor - use nextStartingAfter from previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational context: per-action credit costs (20/20/110), the caveat that costs are indicative and confirmed in response headers, and the cursor round-trip contract. It does not cover failure modes or what happens on an invalid cursor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then pagination contract, then per-action semantics, then cost. Bullets and labeled sections make it scannable, and the two-sentence credit disclaimer is the only mild repetition of the bullet list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only source for response shape, yet it describes returns only loosely ('get address XRP balance') and mentions just one response field (nextStartingAfter). Cost and pagination are well covered, but an agent calling list-transactions has no idea of the record fields or list envelope it will receive.

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 description coverage is 100%, so the baseline is 3, but the description earns an extra point by explaining the meaning of the action enum values (e.g. 'get-next-sequence: Get next available sequence number for transactions') where the schema only repeats the enum names. It also spells out the cross-call relationship between response field 'nextStartingAfter' and the 'startingAfter' parameter, which is semantic glue the schema only states locally.

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?

The description opens with a specific verb and resource ('Query latest XRP (Ripple) address data') and then enumerates the three concrete operations (get-balance, list-transactions, get-next-sequence). The chain qualifier 'XRP (Ripple)' lets an agent distinguish it from the evm/solana/kaspa/utxo siblings without opening the schema.

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

Usage Guidelines4/5

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

The Actions block tells the agent which of the three operations to pick and what each returns conceptually, and the pagination line says exactly what to do on the follow-up call. It stops short of explicit exclusions (e.g., when to prefer a different chain tool or a different pagination strategy), so it is clear context rather than full when/when-not guidance.

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