Skip to main content
Glama
@cryptoapis-io/mcp-transactions-data

@cryptoapis-io/mcp-transactions-data

Official

XRP transaction details

transactions_data_xrp
Read-onlyIdempotent

Retrieve XRP transaction details by hash on mainnet or testnet to verify transfers, inspect ledger data, and support transaction monitoring.

Instructions

Transactions Data XRP: get transaction details by transaction hash. Networks: mainnet, testnet.

Credits per call: 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": {
      "network": "<network>",
      "transactionHash": "<transactionHash>"
    },
    "name": "transactions_data_xrp"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional context for the request - echoed back in response
networkYesNetwork name
transactionHashYesTransaction hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real cost context (110 credits per call, with the actual amount returned in response headers), which is useful beyond annotations. However, it says nothing about failure modes for a missing hash or about rate limits/response shape, so it stays middling.

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 core capability is front-loaded in the first sentence with networks immediately after. The trailing two sentences about indicative credits are boilerplate and slightly diluting, but short enough not to harm scannability.

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?

With three parameters, full schema coverage, rich annotations and no output schema, the definition is adequate for invocation. The main gap is that it never describes what a 'transaction detail' response contains, which matters precisely because there is no output schema.

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 description coverage is 100%, so 'network' (with enum) and 'transactionHash' are already documented structurally; the description only echoes that lookup is by hash. It adds no format, casing or validation detail (e.g., hash length/prefix) beyond the schema, which is the baseline case.

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?

The description names a specific verb and resource ('get transaction details by transaction hash') and scopes it to the XRP networks mainnet/testnet. It is clearly distinguishable from the sibling EVM/Solana/Kaspa/UTXO variants, though that differentiation comes mostly from the tool name and title rather than description text.

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?

Usage is implied: call this to look up a single XRP transaction by its hash on mainnet or testnet. There is no explicit when-to-use vs. when-not guidance, no mention of error behavior for unknown hashes, and no routing advice toward sibling chain tools.

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