Skip to main content
Glama
Sign In
omniroute-bridge-mcp

omniroute-bridge-mcp

Official
by c-viper-work
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_cross_chain_bridge_quote

Read-onlyIdempotent

Fetch a Relay quote with fee breakdown and unsigned steps. Never signs or broadcasts; missing sender creates a preview. Always show executeUrl to the user for 1-click browser wallet signing.

Instructions

Fetch a Relay quote with fee breakdown and unsigned steps. Never signs or broadcasts; missing sender creates a preview. Always show executeUrl to the user for 1-click browser wallet signing.

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

Input Schema

NameRequiredDescriptionDefault
amountYesPositive human-readable source-token amount as a decimal string; no exponent notation. Use strings to preserve precision.
toChainYesSupported chain slug, alias or numeric chain ID as a string (for example base, arb, solana, 8453).
toTokenNoDestination token symbol, native, or raw contract/mint address.
fromChainYesSupported chain slug, alias or numeric chain ID as a string (for example base, arb, solana, 8453).
fromTokenNoSource token symbol such as ETH, USDC or native; amounts are denominated in this token.
slippageBpsNoMaximum slippage in basis points: 50 means 0.50%. Omit for Relay automatic tolerance.
userAddressNoReal sender address on the source chain. Omit only for a read-only preview that cannot be executed.
toTokenDecimalsNoRequired decimal precision for an unregistered raw destination token address.
recipientAddressNoDestination wallet address, matching the destination chain VM. Verify the platform wallet before onboarding.
fromTokenDecimalsNoRequired decimal precision for an unregistered raw source token address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint and destructiveHint=false, so the safety bar is low; the description still adds value by confirming 'Never signs or broadcasts' and explaining that an omitted sender downgrades the call to a non-executable preview. It does not mention rate limits or freshness/expiry of the quote.

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?

Two tight sentences: what is returned first, then the non-signing guarantee and the executeUrl directive. Very little waste, though the 'Always show executeUrl' instruction is a presentation rule rather than a definition concern.

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 10-parameter, no-output-schema tool, the description usefully previews the return shape ('fee breakdown and unsigned steps', executeUrl) and the read-only preview mode. Remaining gaps are minor since token/chain tokenomics and decimals validation are fully covered by the schema.

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 description coverage is 100%, so the schema already documents all ten parameters including the decimals and slippageBps semantics. The description's note that a missing sender yields a preview reiterates what userAddress's schema text already says, adding no new parameter meaning beyond the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description names a specific verb and resource ('Fetch a Relay quote') and enumerates the payload ('fee breakdown and unsigned steps'), which an agent can distinguish from check_bridge_order_status and list_supported_chains_and_tokens. It stops short of explicitly naming the sibling it replaces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It does give real usage direction ('missing sender creates a preview', 'Always show executeUrl to the user for 1-click browser wallet signing'), but that is invocation etiquette rather than routing guidance. No sibling alternative or when-not-to-use condition is stated, so the agent must infer that a quote precedes onboarding and status checks.

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

Deploy Server

Other Tools