Skip to main content
Glama

Bridge routes

bridge_route_optimizer
Read-only

Find the optimal cross-chain bridge route using LI.FI. Compare fees, speed, and output across bridges for any chain pair. Supports ETH, USDC, and custom tokens across Ethereum, Arbitrum, Optimism, Base, Polygon, zkSync, and more. Use toChain='scan' to compare all L2 destinations. Costs $0.01 USDC per call.

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>"
    },
    "name": "bridge_route_optimizer"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoToken to bridge: 'ETH', 'USDC', or token address (default: ETH)ETH
amountNoAmount in human units (e.g. '1.0' for 1 ETH, '1000' for 1000 USDC)1.0
toChainYesDestination chain (e.g. 'optimism', 'polygon'). Use 'scan' to compare all L2s.
fromChainYesSource chain (e.g. 'ethereum', 'arbitrum', 'base')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds behavior not present in annotations: the LI.FI data source and, importantly, a per-call cost of $0.01 USDC, which the agent needs before invoking. It also implicitly frames the tool as a quote/search (consistent with readOnlyHint=true) rather than an execution tool, though it never explicitly says no transaction is submitted.

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?

Four dense sentences with zero filler: purpose, comparison dimensions, supported token/chain surface, scan mode, cost. The most decision-relevant facts (what it does and the scan option) are front-loaded.

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?

With no output schema, the description carries the burden of describing returns and does so at a high level ('fees, speed, and output across bridges'), plus cost and chain coverage. The concrete response shape (single best route vs. ranked list of routes) is left unspecified, which is the only meaningful remaining gap.

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%, so the schema already explains token, amount, fromChain, and toChain including the 'scan' sentinel. The description's chain list (Ethereum, Arbitrum, Optimism, Base, Polygon, zkSync) loosely expands the valid value space beyond the schema's two-example lists, but that is marginal added meaning; baseline 3 applies.

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 and resource ('Find the optimal cross-chain bridge route') plus the underlying source (LI.FI) and what is compared ('fees, speed, and output'). The 'cross-chain' framing cleanly distinguishes it from the same-chain sibling swap_quote.

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?

Gives explicit operational guidance for the 'scan' mode of toChain, which is real when-to-use information an agent would otherwise have to guess. It stops short of naming an alternative (e.g. swap_quote for same-chain swaps) or exclusions, so it is clear context without full routing guidance.

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