Skip to main content
Glama

N9T2 XRPL Agent Gateway

by com.n9t2
OverviewDiscussionsAdmin

n9t2_xrpl_get_ledger

Read-onlyIdempotent

Read-only XRPL ledger header and metadata lookup. Omit ledger_index to use the current validated ledger, or provide a validated ledger index/selector to pin the lookup; set transactions=true to include that ledger's transactions and use expand=true to return those transactions as full objects. The result provides ledger metadata and, when requested, transaction data without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for ledger headers, metadata, and optional ledger transactions; use n9t2_xrpl_get_ledger_data instead when you need raw ledger-state objects.

Input Schema

NameRequiredDescriptionDefault
expandNoWhether returned transactions should be expanded into full transaction objects.
ledger_indexNoOptional validated ledger index or ledger selector. Omit to use the current validated ledger.
transactionsNoWhether to include transactions contained in the requested ledger.

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. Changed3 schema fields changed
    • addedInput schema / properties / expand / description
      Added value: +"Whether returned transactions should be expanded into full transaction objects."
    • addedInput schema / properties / ledger_index / description
      Added value: +"Optional validated ledger index or ledger selector. Omit to use the current validated ledger."
    • addedInput schema / properties / transactions / description
      Added value: +"Whether to include transactions contained in the requested ledger."
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description still adds real context beyond them: the default-to-current-validated-ledger behavior and that calls are subject to configured gateway rate limits. It does not detail response shape or error conditions, keeping it short of 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?

Front-loaded with the core purpose, then behavior, then routing. It is a single dense paragraph with little waste, though the middle sentence packs three clauses and the final 'use this for...' clause partly repeats the opening.

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 still tells the agent what comes back (ledger metadata plus optionally transactions) and how to control it. It stops short of describing pagination or the exact metadata fields, a minor gap for a read-only lookup.

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 the dependency the schema does not state: expand only yields full objects for transactions included via transactions=true. It also restates the omit-ledger_index default in operationally useful terms.

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 ledger header and metadata lookup') and explicitly names the sibling it is not ('use n9t2_xrpl_get_ledger_data instead when you need raw ledger-state objects'). An agent can distinguish this from the other 18 siblings without opening a 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?

Gives an explicit when-to-use plus concrete conditions for each mode: omit ledger_index for the current validated ledger, pin via index/selector, set transactions/expand as needed. It also names the alternative tool and the exact condition that selects it.

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