Skip to main content
Glama

Stoa: swaps on Robinhood Chain

Bridge to Robinhood Chain

bridge_quote
Read-only

Move ETH, USDC or USDT from Base, Arbitrum, Ethereum, Optimism or BNB Chain to the same wallet on Robinhood Chain (arriving as ETH or USDG), through LI.FI over Across. Returns an unsigned transaction on the source chain that Stoa has already decoded: receiver and refund address are the wallet, destination is Robinhood Chain, it spends exactly the amount asked. If 'approval' is present, approve exactly that amount first. Regular wallets only.

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>",
      "fromToken": "<fromToken>",
      "amount": "<amount>",
      "wallet": "<wallet>"
    },
    "name": "bridge_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesInteger amount of fromToken in its smallest unit (18 decimals for ETH and BNB Chain stables, 6 for USDC/USDT elsewhere).
walletYesThe user's wallet: it signs on the source chain and receives on Robinhood Chain.
toTokenNoWhat arrives on Robinhood Chain. Default ETH.
fromChainYesWhere the funds are now.
fromTokenYesETH, USDC, USDT or USDT0, as available on that chain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that the tool returns an unsigned transaction, that the receiver and refund address are the wallet, that the spend is exactly the requested amount, and what to do if an approval object is present. It also names the external routing stack (LI.FI over Across) and excludes non-regular wallets. This is rich behavioral context beyond the annotations.

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 front-loaded with the core action and supported routes, then moves efficiently through return semantics, approval handling, and the wallet restriction. Every sentence adds operational information, and there is no boilerplate or repetition.

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?

There is no output schema, but the description compensates by explaining that the return value is an unsigned transaction with a fixed receiver, refund address, destination chain, and exact spend amount. It does not mention quote expiry, fees, or slippage expectations, which would matter for a bridge quote. Overall it is complete enough to call correctly, with minor economic/quote-lifecycle gaps.

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

Parameters4/5

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

Schema coverage is already 100%, so the schema carries the individual parameter documentation. The description still adds cross-parameter meaning: the wallet signs on the source chain and receives on Robinhood Chain, the amount is spent exactly, and any approval should match that exact amount. These constraints are useful beyond the per-field schema text.

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 states a specific action and scope: move ETH, USDC or USDT from five named source chains to Robinhood Chain via LI.FI/Across. It clearly identifies the returned artifact as an unsigned source-chain transaction, setting it apart from a generic quote or swap-building tool. An agent can tell what this tool is for without opening the schema.

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?

The description implies usage by naming the supported source chains, destination token outcomes, and the 'Regular wallets only' restriction. It also gives an approval-handling instruction. However, it does not explicitly say when to choose this tool over siblings such as quote or build_swap, so routing guidance is mostly implied rather than stated.

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.