Skip to main content
Glama

Polymarket, Kalshi, Hyperliquid Funding Arbitrage & DEX Swap MCP

Quote Cross-Chain USDC Bridge Fee & Net Output

quote_crosschain_usdc_bridge
Read-onlyIdempotent

Quotes live net received USDC, gas cost, and bridge fee across Arbitrum (42161), Base (8453), Optimism (10), Ethereum (1), and Polygon (137) via LI.FI.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quote_crosschain_usdc_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault
toChainIdNoDestination chain ID (e.g. '8453' for Base)
amountUsdcNoAmount of USDC to bridge (e.g. 1000)
fromChainIdNoOrigin chain ID (e.g. '42161' for Arbitrum)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the bar is lower, and the description still adds real value: it discloses the three outputs (net received USDC, gas cost, bridge fee) and that quotes are 'live' rather than cached. It does not disclose quote validity windows, latency, rate limits, or what happens if a route is unsupported — gaps that matter for a live external-aggregator call.

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?

One dense sentence with the resource, the three returned values, the full chain set and the provider — every clause carries information and the core purpose is front-loaded. No filler, no restatement of the title.

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 return-value burden and does name the three fields returned, which is the key completeness need here. Remaining gaps are modest: units/precision of gas cost and amount, and the oddity that no parameters are marked required (which chains are mandatory for a valid quote).

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 baseline is 3; the description goes slightly beyond by enumerating the five valid chain IDs (1, 10, 137, 42161, 8453), which constrains fromChainId/toChainId beyond the schema's two examples. It adds nothing about amountUsdc units (whole USDC vs. base units) or about the fact that all three parameters are optional per the schema.

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?

States a specific verb and resource: quotes net received USDC, gas cost and bridge fee for cross-chain bridging, with the aggregator (LI.FI) and the exact supported chain IDs named. An agent knows exactly what this returns and over which routes. It does not explicitly differentiate from siblings, but the sibling set (kimchi premium, Pendle yields, funding spreads, prediction markets) is disjoint, so that omission is minor.

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?

Usage is only implied by the word 'Quotes' — an agent can infer this is a read-only pre-flight estimate rather than an execution call, and annotations reinforce that. There is no explicit when-to-use statement, no guidance on how it relates to an actual bridge/execute step, and no mention of quote staleness or whether a quote should be refreshed before use.

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.