Skip to main content
Glama

Supported coins

supported_coins
Read-onlyIdempotent

Answers which cryptocurrencies and chains can pay an OpenRouter credit top-up or another AI service invoice through Rozo Checkout: USDC and USDT on Ethereum, BNB Chain, Polygon, Arbitrum and Solana; USDC on Base and Stellar; native ETH (Ethereum, Base, Arbitrum), BNB, POL and SOL; BTC over Lightning; USDT and TRX on TRON (Beta), USDT on TON. Returns each chain id, token symbol and token decimals (TRON and TON rows carry route "tron_ton_alpha", a beta flag and their fee wording), plus webOnlyRoutes: coins served only on checkout.rozo.ai pages. Static list, needs no payment link and makes no network call; quote_invoice reports which of these a specific invoice accepts. Native coins (ETH on Ethereum, Base, Arbitrum; BNB on BNB Chain; POL on Polygon; SOL on Solana) are exact-out like Lightning: the order states the exact coin amount, priced at the current rate plus an FX spread on top of the service fee, and that price holds only until quoteExpiresAt. Native ETH, BNB and SOL take OpenRouter invoices of up to 10,000 credits (about $10,500; refused only above $12750 of callerPays, service fee included, so a 10,000-credit invoice always fits). POL is capped at $3500 (native ETH on Ethereum needs at least $1), and a native coin is offered only when quote_invoice lists it for that invoice. ZEC on Zcash is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec. On-chain BTC (the Bitcoin network, Beta) is not available through this server either; the lightning chain id here is Bitcoin Lightning only. Send a payer who wants to pay on-chain to https://checkout.rozo.ai/btc-onchain. USDT and TRX on TRON (Beta) and USDT on TON go through a dedicated route (route "tron_ton_alpha", the same backend as checkout.rozo.ai/tron and /ton): create_deposit_order returns one exact amount, a receiving address and, on TON when required, a six digit comment, valid until expiresAt. TRON Beta charges 1% with a $0.30 minimum; TON charges 1%; the exact fees come with the order. These orders have no rozoPaymentId: check them with payment_status and the payment link url. Availability can change; quote_invoice reports whether TRON and TON are open for a given invoice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "supported_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish read-only, non-destructive, idempotent, closed-world behavior, and the description adds substantial context beyond that. It explains return fields, beta routes, fee behavior for TRON and TON, native-coin exact-out semantics, quoting constraints, and that these orders lack rozoPaymentId and should be checked with payment_status.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded, but the description is far longer than needed for a no-argument static list and packs many order-pricing and route details into one dense block. It also repeats TRON/TON route and fee information, which reduces conciseness even though most details are relevant.

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 no-parameter static capability list with annotations covering safety and no output schema, the description is more than complete. It covers supported assets, return fields, beta routes, native-coin constraints, and the relationship to quote_invoice and payment_status.

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?

The tool has zero parameters, so there are no parameter semantics for the description to clarify. The baseline for zero-parameter tools is 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?

The description opens with a specific verb and resource: it answers which cryptocurrencies and chains can pay an OpenRouter credit top-up or another AI service invoice through Rozo Checkout. It also distinguishes this static list from quote_invoice, which reports what a specific invoice accepts.

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?

It explicitly says to use this static list without a payment link or network call, and to use quote_invoice to check a specific invoice. It also gives clear exclusions, directing ZEC and on-chain BTC payers to external URLs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.