Skip to main content
Glama
Sign In

ScanHood

by xyz.scanhood
OverviewDiscussionsAdmin

Get a cross-chain bridge quote

get_bridge_quote

Read-only quote (no execution) for bridging native ETH/BNB between Robinhood Chain and Ethereum, Base, Arbitrum, or BNB Chain, via relay.link — the same route ScanHood's own Bridge tab uses. No ScanHood fee. Returns amountOut, an ETA in seconds, relay's own fee in USD, and the raw unsigned deposit tx (to/value/data) for the caller's own wallet to sign and send on the fromChain — ScanHood never holds funds or keys.

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_bridge_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNowallet address that will send the bridge — improves quote accuracy, optional
amountYesnative-token amount to bridge (ETH, or BNB if fromChain is 56), as a decimal string
toChainYesdestination chain id — same supported set as fromChain, must differ from it
fromChainYessource chain id — one of 4663 (Robinhood), 1 (Ethereum), 8453 (Base), 42161 (Arbitrum), 56 (BNB Chain)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explicitly states the tool is read-only, does not execute, never holds funds or keys, and returns an unsigned transaction for the caller to sign and send. This is exemplary transparency.

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 compact, front-loaded with the core purpose, and every phrase adds value—chains, provider, fee status, return values, and security guarantee. There is no redundant or filler text.

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?

Since there is no output schema, the description adequately enumerates the key return values: amountOut, ETA in seconds, relay fee in USD, and the raw unsigned deposit tx. It also covers the execution model, making the tool fully understandable for safe use.

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?

The input schema already covers all parameters with descriptions and chain IDs, achieving 100% schema coverage. The tool description adds no extra parameter-level semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 read-only cross-chain bridge quote, enumerates the exact chains, and calls out relay.link as the provider. This distinguishes it from siblings like get_swap_quote by explicitly noting no execution and the bridge-specific scope.

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 gives strong usage context: use this for read-only bridging quotes over the same route as ScanHood's Bridge tab, with no ScanHood fee. However, it does not explicitly name alternatives or state when not to use this tool versus get_swap_quote or other execution tools.

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

All ScanHood toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources