Skip to main content
Glama
Sign In

N9T2 XRPL Agent Gateway

by com.n9t2
OverviewDiscussionsAdmin

n9t2_xrpl_list_account_lines

Read-onlyIdempotent

Read-only XRPL trust-line lookup for one account. account is the required XRPL classic account address; use peer to restrict results to one counterparty, limit to cap returned trust lines, marker to continue pagination from a previous response, and ledger_index to pin the lookup to a validated ledger. The result lists trust-line state including issued-asset balances and limits without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for an account's trust lines and issued-asset holdings; use n9t2_xrpl_get_account_info for current account state or n9t2_xrpl_list_account_objects for other ledger objects.

Input Schema

NameRequiredDescriptionDefault
peerNoOptional XRPL classic account address used to filter trust lines to a specific peer.
limitNoOptional maximum number of trust lines to return.
markerNoPagination marker returned by a previous response.
accountYesXRPL classic account address whose trust lines should be listed.
ledger_indexNoOptional validated ledger index or selector.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed5 schema fields changed
    • addedInput schema / properties / account / description
      Added value: +"XRPL classic account address whose trust lines should be listed."
    • addedInput schema / properties / ledger_index / description
      Added value: +"Optional validated ledger index or selector."
    • addedInput schema / properties / limit / description
      Added value: +"Optional maximum number of trust lines to return."
    • addedInput schema / properties / marker / description
      Added value: +"Pagination marker returned by a previous response."
    • addedInput schema / properties / peer / description
      Added value: +"Optional XRPL classic account address used to filter trust lines to a specific peer."
  4. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds real value beyond them: it states the ledger is not modified, that calls are subject to configured gateway rate limits, and that the result lists trust-line state with issued-asset balances and limits. It stops short of describing error behavior or response shape, but this is well above the annotation baseline.

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-loads the purpose, then parameter roles, then return/behavioral notes, then sibling routing. Dense but every clause earns its place with 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?

No output schema exists, so the description compensates by describing what the result contains (trust-line state, issued-asset balances and limits). With read-only safety covered by annotations, an agent has everything needed to invoke it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: peer 'restricts results to one counterparty', limit 'caps returned trust lines', marker 'continues pagination from a previous response', ledger_index 'pins the lookup to a validated ledger'. These are functional roles, not restatements.

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 trust-line lookup for one account') and immediately names the two sibling tools it is not (get_account_info, list_account_objects). An agent can distinguish it from the other list_account_* siblings without opening any schema.

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 routes: use this for trust lines and issued-asset holdings; use n9t2_xrpl_get_account_info for current account state or n9t2_xrpl_list_account_objects for other ledger objects. That is a clear when-to-use with named alternatives.

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 toolsInspect
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