Skip to main content
Glama

Rozo Checkout

by io.github.RozoAI
OverviewDiscussionsAdmin

Quote: fund a Stellar wallet

stellar_wallet_quote
Read-only

Price sending USDC/USDT from Base, Ethereum, Arbitrum or Polygon to USDC on a Stellar address. If the address is new or has no USDC trustline, the same plan opens the account, adds the trustline and (with usdGas) gives XLM, in one transaction the address signs once. Returns quoteId and planDigest (needed by stellar_wallet_create_order), the USDC and XLM amounts the receiver gets, every fee line and totals, and whether a signature will be needed. Valid about 10 minutes. Read-only: no deposit address, nothing reserved. usdGas: "0" no XLM, "0.5" or "1" buys XLM (see funding_capabilities for amounts); omitted = the server default. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.

Input Schema

NameRequiredDescriptionDefault
usdGasNoUSD of XLM for fees. Omit to use the server default.
amountUsdYesAmount you will send, as a decimal string in USD, e.g. "10" or "10.50". Limits come from funding_capabilities (1 to 1000 today).
sourceChainYesChain you will pay from.
receiverAddressYesStellar PUBLIC address (G...) that receives the USDC. Never a secret key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover safety (readOnlyHint, destructiveHint false), but the description adds rich behavioral context: ~10-minute validity, no deposit address or reservation, signing requirement triggers, server never holds keys, fee handling, and deposit amountPolicy. This is well beyond what annotations provide.

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?

Dense but front-loaded, starting with purpose and returns. Some repetition (the signing condition and chain list appear twice), which keeps it from 5; still, every sentence carries operational detail needed without an output schema.

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?

Given cross-chain quote complexity and no output schema, the description must convey return values and next steps; it does (quoteId, planDigest, amounts, fees, totals, signature need) plus validity, payment policy, and key custody. Complete.

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 baseline is 3. The description adds meaning beyond the schema for usdGas ('0', '0.5', '1' behaviors), amountUsd limits, shared deposit address across chains, and the receiving address's signing role, meriting a 4.

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 ('Price sending') and resource (USDC/USDT from Base, Ethereum, Arbitrum or Polygon to USDC on Stellar). It routes to sibling stellar_wallet_create_order by noting quoteId and planDigest are needed there, distinguishing its role as the quote step.

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?

Provides clear context: the quote is needed by stellar_wallet_create_order and limits come from funding_capabilities. It does not explicitly say when not to use it or compare with quote_invoice, so it stops short of full alternative routing.

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

All Rozo Checkout 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