Skip to main content
Glama

get_bridge_quote

Obtain a bridge quote for transferring the same token between chains. Returns transaction data steps for direct signing or a deep link for manual fallback.

Instructions

Get a quote for bridging the SAME token from one chain to another (e.g. ETH on Ethereum → ETH on Base).

Use this for same-token cross-chain transfers. For different tokens (same or cross-chain), use get_swap_quote instead.

Returns execution steps — each step contains ready-to-sign transaction data (to, data, value, chainId, gas). An agent with wallet tooling can sign and submit these directly. Also returns a relay.link deep link as a fallback for manual execution.

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
NameRequiredDescriptionDefault
amountYesAmount to bridge in the token's smallest unit. Examples: "1000000000000000000" for 1 ETH (18 decimals), "100000000" for 1 BTC (8 decimals).
senderYesSender wallet address.
currencyYesToken address or symbol to bridge. Symbols like "ETH", "USDC", "USDT", "WETH" are resolved automatically. 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.
refundToNoAddress to send refunds to if the bridge fails. Defaults to sender. Useful when sender is a deposit address or contract.
recipientNoRecipient wallet address. Defaults to sender if not provided.
tradeTypeNoEXACT_INPUT (default): you specify input amount, output varies. EXPECTED_OUTPUT: you specify desired output, input is calculated (allows slippage). EXACT_OUTPUT: you specify exact output required, fails if not deliverable.EXACT_INPUT
includeStepsNoInclude raw transaction steps for signing. Only needed if you have wallet tooling to submit transactions directly. Omit to save tokens.
originChainIdYesSource chain ID or name (e.g. 1, 'ethereum', 'eth').
useDepositAddressNoUse deposit address flow — returns an address the user can send funds to (e.g. from a CEX or wallet) instead of transaction calldata. No wallet signing needed. The deposit address is reusable for the same origin→destination→currency route. Only supports EXACT_INPUT. Adds ~33k gas for native tokens, ~70k for ERC-20s.
destinationChainIdYesDestination chain ID or name (e.g. 8453, 'base').
Behavior5/5

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

With no annotations, description explains that it returns execution steps with ready-to-sign transaction data and a deep link. Covers trade types, deposit address flow, and default behaviors, making tool behavior fully transparent.

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?

Well-structured with clear sections, but slightly verbose given the number of parameters. Could be tightened without losing clarity.

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 tool with 10 parameters and no output schema or annotations, the description covers purpose, usage, parameter details, return behavior, and multiple execution modes. Very complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: examples for amount units, explanation of currency resolution (symbols, native addresses), tradeType enum details, chain ID flexibility, and deposit address flow mechanics.

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?

Clearly states it gets a quote for bridging the same token across chains. Explicitly distinguishes from get_swap_quote for different tokens.

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?

Explicitly tells when to use (same-token cross-chain) and when not (different tokens, use get_swap_quote). Provides detailed guidance on amount units, chain IDs, and token symbols.

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

Install Server

Other Tools

Latest Blog Posts

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