Swapper - XMR to USDC swaps

Get XMR/USDC swap quote

get_quote

Read-onlyIdempotent

Step 1. Quote Monero (XMR) <-> native USDC on Arbitrum One; no account or API key. Creates no order. Quotes are estimates. Buy XMR ("get me 1 XMR"): {direction:"u2x", receiveAmount:"1"}. Sell XMR: {direction:"x2u", amount:"0.5"}. direction plus exactly one of amount (what the user sends) or receiveAmount (what they want). Pass to if known. Next: create_swap with next.arguments.

Input Schema

Name	Required	Description
`to`	No	Destination from the user: x2u an Arbitrum One 0x address, u2x a Monero address. Never guess.
`basis`	No	receiveAmount met by the estimate (default) or the provider minimum (if published).
`chain`	No	Default arbitrum (42161).
`amount`	No	What the user SENDS (x2u: XMR, u2x: USDC). Digits and one dot; no commas or units.
`detail`	No
`agentKey`	No	Optional key from request_agent_key.
`direction`	No	Required. u2x: send USDC, get XMR. x2u: send XMR, get USDC.
`requoteOf`	No	Re-quote this quoteId's stored parameters; pass it alone.
`receiveAmount`	No	What the user wants to RECEIVE (u2x: XMR, x2u: USDC); needs direction.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`next`	Yes
`delta`	No
`error`	No
`quote`	No
`state`	No
`target`	No
`quoteId`	No
`agentKey`	No
`direction`	No
`operation`	Yes
`guaranteed`	No
`acceptUntil`	No
`destination`	No
`userMessage`	No
`expiresInSec`	No
`prerequisites`	No
`minimumSwapUsd`	No
`acceptWindowSec`	No
`belowProviderMinimum`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / agentKey / description

Previous value: -"From request_agent_key: lower fee."New value: +"Optional key from request_agent_key."

changedInput schema / properties / basis / description

Previous value: -"receiveAmount target met by the estimate (default) or the provider minimum (only if one is published)."New value: +"receiveAmount met by the estimate (default) or the provider minimum (if published)."

Changed2 schema fields changedOct 13, 2026

addedInput schema / properties / agentKey

Added value: +{
+  "description": "From request_agent_key: lower fee.",
+  "pattern": "^swk_[a-f0-9]{40}$",
+  "type": "string"
+}

addedOutput schema / properties / agentKey

Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}

First observedOct 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so safety is covered, but the description adds meaningful context: it needs no account or API key, it creates no order, and quotes are estimates only. That estimate caveat is important behavioral context not derivable from annotations.

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 'Step 1' and the core purpose, then adds compact, high-value usage examples. Slightly dense with parenthetical quotes and shorthand, but every sentence carries information and none is wasted.

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?

An output schema exists so return values needn't be explained, and the description still hints at the handoff ('next.arguments'). Combined with the parameter examples and estimate caveat, it is complete enough for an agent to call correctly; only minor detail like the 'detail' enum meaning is absent.

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 high (89%), so the schema documents most parameters. The description goes beyond it by giving concrete invocation examples ('get me 1 XMR' -> direction:"u2x", receiveAmount:"1") and stating the direction+exactly-one-of rule, adding value over the raw schema.

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?

Names a specific verb (Quote) and resource (XMR <-> native USDC on Arbitrum One), and distinguishes itself from siblings by stating 'Step 1' and 'Creates no order', separating it from create_swap/plan_swap. An agent can identify the tool's role 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?

Positions the tool as the first step of a flow and explicitly names the follow-on ('Next: create_swap with next.arguments'), routing the agent to the correct sibling. It also clarifies 'no account or API key' and 'Creates no order', which further delineates when to use it versus mutation tools.

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

All Swapper - XMR to USDC swaps tools Inspect

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

Need Help?