Skip to main content
Glama
Sign In

AgentTrust

by io.github.eamwhite1
OverviewDiscussionsAdmin
This connector has been deprecated

This connector has been replaced by xrpl-referee.

Get DEX Quote

get_dex_quote
Read-onlyIdempotent

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

Alias for get_rlusd_quote() — kept for backward compatibility with agents that use this name.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "xrp_amount": "<xrp_amount>",
      "worker_address": "<worker_address>"
    },
    "name": "get_dex_quote"
  }
}

Input 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the bar is lower. The description still adds real behavioral value by disclosing that the call yields a live, externally-sourced DEX rate and performs a trustline check (trust_line_ok, trust_line_instructions), which signals a side effect of validation rather than a pure lookup.

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-loaded with the core action and scoped with a single usage sentence. The explicit return-value list at the end is largely redundant with the existing output schema, which is the only wasted space.

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?

With annotations, an output schema and full parameter coverage, the description only needs to frame intent, which it does. Minor gap: a 'live' quote is time-sensitive, yet there is no indication of quote validity or refresh cadence, though that may be carried by the output schema.

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% and both parameters are already documented, including that worker_address is used to check trustline status. The description adds no syntax, format, or bounds information beyond that, so the baseline 3 applies.

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: 'Get a live XRP to RLUSD conversion quote via the XRPL DEX.' It also resolves the identity question an agent would have by declaring itself an alias of get_rlusd_quote(), which is the sibling it overlaps with.

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 triggering contexts ('before creating an RLUSD-denominated escrow or before claiming an escrow') tied to a concrete agent goal. It does not name when an agent should prefer get_rlusd_quote instead, leaving that routing decision implicit in the alias note.

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

All AgentTrust 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