Skip to main content
Glama
Sign In

N9T2 XRPL Agent Gateway

by com.n9t2
OverviewDiscussionsAdmin

n9t2_xrpl_get_amm_info

Read-onlyIdempotent

Read-only XRPL Automated Market Maker (AMM) state lookup for a specific pool. Identify the pool with amm_account, or with the paired asset and asset2 currency objects; account is optional context used by the native AMM lookup when applicable. Use ledger_hash or ledger_index to pin the lookup to a specific ledger. The result returns native amm_info data including pool balances, LP token supply, trading fee, auction slot, and vote slots when present. This paid lookup does not modify the ledger and is subject to the configured gateway rate limits. Use this for AMM pool state; use n9t2_xrpl_get_book_offers for DEX order-book depth and n9t2_xrpl_get_ledger_data for raw ledger-state objects.

Input Schema

NameRequiredDescriptionDefault
assetNoFirst AMM asset specification using an XRPL currency object.
asset2NoSecond AMM asset specification paired with asset.
accountNoOptional XRPL account used by the native AMM lookup when applicable.
amm_accountNoOptional AMM account address identifying the specific AMM ledger object.
ledger_hashNoOptional ledger hash used to pin the AMM lookup to a specific ledger.
ledger_indexNoOptional ledger index or selector used to pin the lookup to a specific 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. Changed6 schema fields changed
    • addedInput schema / properties / account / description
      Added value: +"Optional XRPL account used by the native AMM lookup when applicable."
    • addedInput schema / properties / amm_account / description
      Added value: +"Optional AMM account address identifying the specific AMM ledger object."
    • addedInput schema / properties / asset / description
      Added value: +"First AMM asset specification using an XRPL currency object."
    • addedInput schema / properties / asset2 / description
      Added value: +"Second AMM asset specification paired with asset."
    • addedInput schema / properties / ledger_hash / description
      Added value: +"Optional ledger hash used to pin the AMM lookup to a specific ledger."
    • addedInput schema / properties / ledger_index / description
      Added value: +"Optional ledger index or selector used to pin the lookup to a specific ledger."
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered. The description adds genuinely new context: it is a paid lookup, it does not modify the ledger, it is subject to gateway rate limits, and it returns native amm_info with pool balances, LP token supply, fee, auction slot and vote slots. That is meaningful behavior beyond what annotations convey.

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 description is dense but front-loaded: purpose first, then pool identification, then ledger pinning, then return shape, then sibling routing. Every sentence carries information, though it is on the longer side.

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?

With no output schema, the description compensates by enumerating the return fields (balances, LP supply, fee, auction slot, vote slots). Combined with the parameter model and rate-limit note, an agent has everything needed to call and interpret it.

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 3 is the baseline, but the description adds real meaning by explaining the two alternative pool-identification paths (`amm_account` OR the paired `asset`/`asset2`), that `account` is optional context, and that ledger_hash/ledger_index pin the lookup. This reconciliation goes beyond the per-field schema text.

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 ('Read-only XRPL Automated Market Maker (AMM) state lookup for a specific pool') and explicitly distinguishes itself from two named siblings, n9t2_xrpl_get_book_offers and n9t2_xrpl_get_ledger_data. An agent can route to it 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 alternatives and the conditions that select them: use this for AMM pool state, use get_book_offers for DEX order-book depth, use get_ledger_data for raw ledger-state objects. Nothing is left to inference about when to pick this tool.

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