Skip to main content
Glama
Sign In

N9T2 XRPL Agent Gateway

by com.n9t2
OverviewDiscussionsAdmin

n9t2_xrpl_get_gateway_balances

Read-onlyIdempotent

Read-only XRPL issued-asset exposure calculation for one issuing account. account is the required XRPL issuer address; optionally use hotwallet with one address or a list of operational hot-wallet addresses when those balances should be included in the calculation, and use ledger_index to pin the calculation to a specific ledger. strict controls how account identifiers are interpreted. The result reports the calculated issued-asset exposure without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this for issuer-level issued-asset exposure; do not use it for trust-line holdings of a single account, where n9t2_xrpl_list_account_lines is the appropriate tool.

Input Schema

NameRequiredDescriptionDefault
strictNoWhether account identifiers should be interpreted strictly as supplied.
accountYesXRPL issuing account whose issued-asset balances should be calculated.
hotwalletNoOptional XRPL hot-wallet account address or list of hot-wallet addresses.
ledger_indexNoOptional ledger index or selector for the balance calculation.

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. Changed4 schema fields changed
    • addedInput schema / properties / account / description
      Added value: +"XRPL issuing account whose issued-asset balances should be calculated."
    • addedInput schema / properties / hotwallet / description
      Added value: +"Optional XRPL hot-wallet account address or list of hot-wallet addresses."
    • addedInput schema / properties / ledger_index / description
      Added value: +"Optional ledger index or selector for the balance calculation."
    • addedInput schema / properties / strict / description
      Added value: +"Whether account identifiers should be interpreted strictly as supplied."
  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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is largely covered; the description's "without modifying the ledger" is largely redundant. It does add genuinely new behavioral context, though: calls are subject to configured gateway rate limits, and the result is a computed exposure figure rather than raw ledger entries.

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 purpose and scope come first, followed by parameter behavior, then the safety/limits note, then the sibling exclusion — a sensible front-loaded order. It is dense with back-to-back clauses and slightly longer than needed, but no sentence is filler.

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?

For a read-only calculation tool with no output schema, the description covers what is returned (the calculated exposure), safety, rate limits, and the nearest alternative tool. It omits pagination/return-format detail and does not explain what a "strict" interpretation changes, which is a minor gap.

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 semantic intent beyond the schema text: hotwallet addresses are those whose balances "should be included in the calculation," and ledger_index "pins the calculation to a specific ledger." It does not, however, clarify strict's interpretation semantics beyond the schema wording.

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 states a specific verb and resource ("issued-asset exposure calculation for one issuing account") and explicitly contrasts itself with the sibling tool n9t2_xrpl_list_account_lines. An agent can distinguish it from the other list_* / get_* 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?

It gives explicit positive routing ("Use this for issuer-level issued-asset exposure") and an explicit exclusion with a named alternative ("do not use it for trust-line holdings of a single account, where n9t2_xrpl_list_account_lines is the appropriate tool"). It also explains the conditions under which the optional hotwallet and ledger_index parameters should be used.

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