Skip to main content
Glama

Cross chain quote

cross_chain_quote
Read-onlyIdempotent

Live multichain bridge and swap quote via LI.FI across supported EVM & Solana chains (with custom routing notes for X1 and Arc): estimated output USD, total fees, duration, execution steps, and unsigned tx when fromAddress is supplied. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "fromChain": "<fromChain>",
      "toChain": "<toChain>",
      "fromToken": "<fromToken>",
      "toToken": "<toToken>",
      "amount": "<amount>"
    },
    "name": "cross_chain_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesexact input amount in atomic base units (e.g. 10000000 = 10 USDC)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
toChainYesdestination chain slug or ID (e.g. base, arbitrum, optimism, polygon, solana, arc, x1)
toTokenYesdestination token symbol or contract/mint address
slippageNooptional max fractional slippage (0.0001 to 0.5, default 0.005)
fromChainYessource chain slug or ID (e.g. ethereum, base, arbitrum, optimism, polygon, bnb, solana, arc, x1)
fromTokenYessource token symbol (e.g. USDC, ETH, SOL) or contract/mint address
toAddressNooptional recipient wallet (EVM 0x or Solana base58)
fromAddressNooptional sender wallet (EVM 0x or Solana base58) to generate unsigned transactionRequest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds material behavior an agent could not infer: the $0.003 per-call x402 charge, the accepted payment assets/chains, the two-call sign-then-submit pattern, and the fact that an unsigned transactionRequest is only produced when fromAddress is supplied. The readOnly annotation is consistent with a quote tool that returns an unsigned tx rather than submitting it.

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?

The core capability and return fields are front-loaded in the first clause, and the payment protocol follows in a short, actionable second sentence. The parenthetical about X1 and Arc routing notes is slightly vague and consumes space without fully resolving what the agent should do differently, but otherwise there is no filler.

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 9-parameter, no-output-schema tool, the description covers the essentials: what is returned, the paid two-step invocation, the cost, and the conditional tx output. The one soft spot is the unspecific 'custom routing notes for X1 and Arc' phrasing, which hints at special-casing without saying how the agent should act on it.

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 coverage is 100% — every parameter, including amount in atomic units, slippage bounds, and the payment payload, is already documented in the schema. The description reinforces the workflow role of `payment` and the `fromAddress`-gated tx generation but adds no format or constraint detail beyond what the schema states. Baseline 3 is appropriate 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.

Purpose5/5

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

The description states a specific verb and resource — a live multichain bridge/swap quote via LI.FI — and enumerates what it returns (output USD, fees, duration, execution steps, unsigned tx). It also scopes the chain coverage (EVM & Solana, with X1/Arc routing notes), which no sibling tool in the list covers, so an agent can distinguish it from price or EVM read tools 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit procedural guidance: call once without `payment` to get terms, sign with your own wallet, then call again with `payment` to complete the purchase. That removes the main ambiguity about the paid flow. It stops short of naming when to prefer this over alternatives (e.g. a plain price tool) or when a quote is not appropriate, so it is clear context rather than full when/when-not routing.

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.

Resources