Relay MCP Server

get_multi_input_quote

Consolidate tokens from multiple origin chains into a single destination chain and token. Specify origins (chain, token, amount) and destination for portfolio rebalancing.

Instructions

Get a quote for consolidating tokens from MULTIPLE origin chains into a single destination (e.g. USDC from Ethereum + Arbitrum + Optimism → USDC on Base).

Use this for portfolio consolidation, rebalancing, or collecting scattered funds. Each origin specifies its own chain, token, and amount. All origins settle to one destination chain and token.

Amounts must be in the token's smallest unit (wei, satoshis, lamports). Examples: 1 ETH = "1000000000000000000" (18 decimals), 1 USDC = "1000000" (6 decimals), 1 BTC = "100000000" (8 decimals), 1 SOL = "1000000000" (9 decimals). Use convert_amount or get_supported_tokens to look up decimals. Chain IDs can be numbers (8453) or names ('base', 'ethereum', 'arb', 'bitcoin', 'solana').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sender`	Yes	Sender wallet address (must hold funds on all origin chains).
`origins`	Yes	Array of origin sources (minimum 2). Each specifies a chain, token, and amount to consolidate.
`partial`	No	Allow partial fills — if one origin fails, others still execute.
`recipient`	No	Recipient wallet address. Defaults to sender.
`tradeType`	No	EXACT_INPUT (default): origin amounts are inputs. EXPECTED_OUTPUT: total amount is desired output.	EXACT_INPUT
`includeSteps`	No	Include raw transaction steps for signing. Omit to save tokens.
`destinationChainId`	Yes	Destination chain ID or name (e.g. 8453, 'base').
`destinationCurrency`	Yes	Destination token address or symbol (e.g. "USDC", "ETH"). For native tokens use: EVM "0x0000000000000000000000000000000000000000", Solana "11111111111111111111111111111111", Bitcoin "bc1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqmql8k8", Hyperliquid "0x00000000000000000000000000000000", Lighter "0". For other tokens, use the contract/mint address or look up via get_supported_tokens.

Tool Definition Quality

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes that origins must be at least 2, each specifies chain/token/amount, and amounts must be in smallest units. It implies read-only (quote). However, it does not disclose failure modes, rate limits, or what happens if inputs are invalid.

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

Conciseness5/5

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

The description is concise, well-structured, and front-loads the main purpose. Every sentence adds value without unnecessary words.

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?

Given the complexity (8 parameters, no output schema), the description is fairly complete. It explains the overall purpose, input constraints, amount units, and chain ID formats. It does not describe the return value, which is common for quote tools.

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 significant meaning beyond the schema by explaining the multi-origin concept, giving examples of amount units and chain ID formats, and clarifying the purpose of each parameter.

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 clearly states the tool gets a quote for consolidating tokens from multiple origin chains into a single destination. It uses specific verbs ('get a quote') and resources ('consolidating tokens'), and distinguishes from siblings like get_swap_quote by focusing on multi-origin consolidation.

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 explicitly states when to use (portfolio consolidation, rebalancing, collecting scattered funds) and provides guidance on amounts (smallest units) and chain IDs. Mentions alternatives like convert_amount and get_supported_tokens for decimals, but does not explicitly exclude other tools.

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

Install Server

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pedromcunha/relay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server