Skip to main content
Glama

N9T2 XRPL Agent Gateway

by com.n9t2
OverviewDiscussionsAdmin

n9t2_xrpl_get_transaction

Read-onlyIdempotent

Read-only XRPL transaction lookup for one canonical transaction hash. transaction is the required hash; set binary=true only when binary-encoded transaction data is required, otherwise use the normal transaction representation. The result retrieves transaction data for that hash without modifying the ledger, and calls are subject to the configured gateway rate limits. Use this when the transaction hash is already known; use n9t2_xrpl_list_account_transactions for account-wide transaction history instead.

Input Schema

NameRequiredDescriptionDefault
binaryNoWhether to return the transaction in binary encoded form.
transactionYesCanonical XRPL transaction hash to retrieve.

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. Changed2 schema fields changed
    • addedInput schema / properties / binary / description
      Added value: +"Whether to return the transaction in binary encoded form."
    • addedInput schema / properties / transaction / description
      Added value: +"Canonical XRPL transaction hash to retrieve."
  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, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds a useful rate-limit disclosure ('calls are subject to the configured gateway rate limits') and reinforces non-modification, though it does not characterize return format or error behavior.

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?

Four purposeful sentences with the core identity front-loaded. Parameter guidance, result behavior, and alternative routing are all included without 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 simple read-only lookup with rich annotations and full schema coverage, the description is nearly complete. The only minor gap is that no output schema exists and the description does not characterize the returned transaction data structure.

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 adds conditional meaning for binary ('set binary=true only when binary-encoded transaction data is required, otherwise use the normal transaction representation') beyond the schema's plain boolean description.

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 ('Read-only XRPL transaction lookup') and resource ('one canonical transaction hash'), and explicitly distinguishes itself from the account-wide sibling. An agent can identify the tool's scope without opening the 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?

Provides explicit when-to-use guidance ('Use this when the transaction hash is already known') and names the alternative tool for account-wide history ('use n9t2_xrpl_list_account_transactions instead'). It also clarifies the conditional use of the binary parameter.

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