Skip to main content
Glama
eamwhite1

AgentTrust

by eamwhite1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get DEX Quote

get_dex_quote
Read-onlyIdempotent

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

Instructions

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 changedv3.1.0
    • 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.",
+  "title": "Worker XRPL Address",
+  "type": "string"
+}
    • addedInput schema / properties / xrp_amount
      Added value: +{
+  "description": "Amount of XRP to get a conversion quote for.",
+  "exclusiveMinimum": 0,
+  "title": "XRP Amount",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "from_currency",
-  "to_currency",
-  "amount"
-]New value: +[
+  "xrp_amount",
+  "worker_address"
+]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the quote is 'live' and sourced from the XRPL DEX, which is useful context, but it says nothing about quote freshness/staleness or latency, and it repeats return fields already implied by the output schema.

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?

Front-loads the core purpose, then usage context, then a return summary in three compact sections with no filler. Slightly wasteful in re-listing return fields that the output schema already carries, but overall tight and well-ordered.

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 quote tool with a full output schema and complete parameter coverage, the description is nearly complete: it explains purpose, timing, and rough output. The one meaningful gap is that it never distinguishes itself from the confusingly similar get_rlusd_quote sibling, which an agent must resolve to select correctly.

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 xrp_amount and worker_address, including the note that worker_address is used to check trustline status. The description adds no parameter-level detail beyond the schema, making the baseline 3 correct when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb, resource, and mechanism: 'Get a live XRP to RLUSD conversion quote via the XRPL DEX.' This is concrete and actionable. However, it does not differentiate itself from the nearly identical sibling get_rlusd_quote (nor from get_xrp_price), so an agent cannot disambiguate the two quote tools from the text alone.

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?

Gives clear when-to-use context: 'before creating an RLUSD-denominated escrow or before claiming an escrow if you want to understand the current USD value.' That is solid situational guidance. It stops short of naming alternatives (e.g., get_rlusd_quote) or stating when this tool is NOT the right choice.

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

Deploy Server

Other Tools