Skip to main content
Glama

N9T2 XRPL Agent Gateway

by com.n9t2
OverviewDiscussionsAdmin

n9t2_xrpl_find_path

Read-onlyIdempotent

Read-only XRPL payment-path discovery for planning a Payment from source_account to destination_account. destination_amount is the exact amount the destination should receive, provided as XRP drops or an issued-currency object; the result returns candidate path alternatives and source-amount information to compare before constructing the payment. Use this when XRPL routing is needed between the source and destination accounts; use n9t2_xrpl_get_book_offers for DEX order-book depth instead. This tool only discovers paths and does not construct, sign, submit, or modify any XRPL transaction; after selecting a route, use n9t2_xrpl_prepare_transaction to build the unsigned payment.

Input Schema

NameRequiredDescriptionDefault
source_accountYesXRPL classic account address used as the source of payment-path discovery.
destination_amountYesDestination amount to deliver. Use a string for XRP drops or an issued-currency object containing currency, issuer, and value.
destination_accountYesXRPL classic account address that will receive the destination amount.

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 / destination_account / description
      Added value: +"XRPL classic account address that will receive the destination amount."
    • addedInput schema / properties / destination_amount / description
      Added value: +"Destination amount to deliver. Use a string for XRP drops or an issued-currency object containing currency, issuer, and value."
    • addedInput schema / properties / source_account / description
      Added value: +"XRPL classic account address used as the source of payment-path discovery."
  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=false, so the safety profile is covered. The description adds genuinely new behavioral context: it does not construct, sign, submit or modify any transaction, and it discloses the result shape (candidate path alternatives plus source-amount information). Only the auth/rate-limit dimension is unaddressed.

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 that each carry distinct information: purpose/scope, parameter semantics, routing to alternatives and follow-ups. Slightly dense but no filler or repetition.

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?

For a 3-parameter read-only discovery tool with no output schema, the description covers what it returns, what it deliberately does not do, and the correct follow-up tool. Nothing an agent needs in order to call it correctly is missing.

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. The description still adds meaning beyond the schema by defining destination_amount as the exact amount the destination should receive and by clarifying the two accepted encodings in terms of intent rather than just types.

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 payment-path discovery) plus scope (source_account to destination_account) and explicitly distinguishes itself from n9t2_xrpl_get_book_offers. An agent can separate this from the other 17 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?

Explicit when-to-use ('when XRPL routing is needed between the source and destination accounts'), an explicit alternative with its own condition ('use n9t2_xrpl_get_book_offers for DEX order-book depth instead'), and a named follow-up tool (n9t2_xrpl_prepare_transaction) for the next step.

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