Skip to main content
Glama

xrpl-referee

by io.github.eamwhite1
OverviewDiscussionsAdmin

Get DEX Quote

get_dex_quote
Read-onlyIdempotent

Get a live XRP to RLUSD conversion quote via the XRPL DEX.

Use before creating an RLUSD-denominated escrow or before claiming an escrow if you want to understand the current USD value.

Returns: estimated_rlusd, trust_line_ok, slippage_warning, trust_line_instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xrp_amountYesAmount of XRP to get a conversion quote for.
worker_addressYesYour XRPL wallet address (r...). Also used to check whether your RLUSD trustline is active.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / amount
      Removed value: -{
-  "description": "Amount of the from_currency to quote.",
-  "type": "number"
-}
    • removedInput schema / properties / from_currency
      Removed value: -{
-  "description": "Currency to swap from, e.g. 'XRP' or 'RLUSD'.",
-  "type": "string"
-}
    • removedInput schema / properties / to_currency
      Removed value: -{
-  "description": "Currency to swap to, e.g. 'XRP' or 'RLUSD'.",
-  "type": "string"
-}
    • addedInput schema / properties / worker_address
      Added value: +{
+  "description": "Your XRPL wallet address (r...). Also used to check whether your RLUSD trustline is active.",
+  "type": "string"
+}
    • addedInput schema / properties / xrp_amount
      Added value: +{
+  "description": "Amount of XRP to get a conversion quote for.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "from_currency",
-  "to_currency",
-  "amount"
-]New value: +[
+  "xrp_amount",
+  "worker_address"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the quote is 'live,' the worker_address is used for trustline checking, and the response includes slippage_warning and trust_line_instructions. This helps the agent anticipate conditional behavior without contradicting annotations.

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?

The description is three compact sentences with no filler: the main purpose, a usage context sentence, and a concise return-field list. The most important information is front-loaded, and every sentence earns its place.

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 simple read-only quote tool with two well-documented parameters, rich annotations, and an output schema, the description is complete. It tells the agent when to use it, what it returns, and how trustline status factors in. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents both parameters. The description does not add new parameter-level meaning, but it does clarify the purpose of worker_address indirectly through the trustline-related return fields. This meets the baseline for fully covered schemas.

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 opens with a specific verb and resource: 'Get a live XRP to RLUSD conversion quote via the XRPL DEX.' This clearly states the operation and distinguishes it from sibling tools like get_xrp_price and get_rlusd_quote by specifying the DEX route and the exact asset pair.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool: 'before creating an RLUSD-denominated escrow or before claiming an escrow if you want to understand the current USD value.' It does not name explicit exclusions or alternatives, but the context is clear enough for an agent to decide when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All xrpl-referee 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