N9T2 XRPL Agent Gateway

n9t2_xrpl_list_account_transactions

Read-onlyIdempotent

Read-only XRPL transaction-history lookup for one account over an optional ledger range. Use this for multiple account transactions; use n9t2_xrpl_get_transaction when a transaction hash is already known. ledger_index_min and ledger_index_max narrow the history window, while limit bounds the returned records; when the response includes a pagination marker, more history remains beyond the current page. The result contains account transaction records and does not modify the ledger or submit transactions, and calls are subject to the configured gateway rate limits.

Input Schema

Name	Required	Description
`limit`	No	Optional maximum number of transactions to return.
`account`	Yes	XRPL classic account address whose transaction history should be retrieved.
`ledger_index_max`	No	Optional maximum ledger index for the transaction-history range.
`ledger_index_min`	No	Optional minimum ledger index for the transaction-history range.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "operation": {
-      "title": "Operation",
-      "type": "string"
-    },
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    },
-    "service": {
-      "title": "Service",
-      "type": "string"
-    }
-  },
-  "required": [
-    "service",
-    "operation",
-    "result"
-  ],
-  "title": "_XRPLServiceOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "operation": {
+      "title": "Operation",
+      "type": "string"
+    },
+    "result": {
+      "additionalProperties": true,
+      "title": "Result",
+      "type": "object"
+    },
+    "service": {
+      "title": "Service",
+      "type": "string"
+    }
+  },
+  "required": [
+    "service",
+    "operation",
+    "result"
+  ],
+  "title": "_XRPLServiceOutput",
+  "type": "object"
+}

Changed4 schema fields changedOct 6, 2026

addedInput schema / properties / account / description

Added value: +"XRPL classic account address whose transaction history should be retrieved."

addedInput schema / properties / ledger_index_max / description

Added value: +"Optional maximum ledger index for the transaction-history range."

addedInput schema / properties / ledger_index_min / description

Added value: +"Optional minimum ledger index for the transaction-history range."

addedInput schema / properties / limit / description

Added value: +"Optional maximum number of transactions to return."

AddedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world, so the bar is lower, yet the description still adds real context: it clarifies the call does not modify the ledger or submit transactions, and discloses that calls are subject to configured gateway rate limits and that a pagination marker signals remaining history. That is meaningful operational disclosure beyond the annotations.

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?

Three front-loaded sentences: purpose and sibling routing first, then parameter roles, then safety/pagination/rate-limit notes. Efficient and well ordered, with only mild restatement of schema-documented parameter meanings.

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?

With no output schema, the description compensates by describing the result ('account transaction records') and pagination behavior. Combined with the safety and rate-limit notes, an agent has enough to invoke and interpret this correctly; only richer return-shape detail is absent.

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 all four parameters are already documented. The description restates the roles of ledger_index_min/max (history window) and limit (bounds records) but adds no syntax, format, or default behavior beyond the schema — baseline 3 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 verb and resource ('Read-only XRPL transaction-history lookup for one account') with scope modifiers, and explicitly distinguishes itself from the closest sibling, n9t2_xrpl_get_transaction. An agent can route between history lookup and single-transaction lookup without inspecting 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?

Gives an explicit when-to-use ('multiple account transactions') and names the alternative tool plus the condition that selects it ('when a transaction hash is already known'). This is exactly the routing guidance an agent needs among 18 siblings.

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

All N9T2 XRPL Agent Gateway 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?