Skip to main content
Glama

Stoa: swaps on Robinhood Chain

Quote a swap

quote
Read-only

Compare every venue Stoa routes for this exact amount and return the route it would fill: amountOut (after Stoa's 2 bps fee), minOut for the slippage, price impact and the venues. Read-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": {
      "sellToken": "<sellToken>",
      "buyToken": "<buyToken>",
      "amount": "<amount>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork. Default robinhood.
amountYesAmount to sell, integer in the sell token's smallest unit (wei). 0.01 ETH = 10000000000000000.
buyTokenYesToken to buy: a token address, or "native" for the gas token (ETH on Robinhood Chain, HYPE on Elysium).
sellTokenYesToken to sell: a token address, or "native" for the gas token (ETH on Robinhood Chain, HYPE on Elysium).
slippageBpsNoMax slippage in basis points. Default 50 (0.5%).

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 declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds real value by disclosing that amountOut is net of Stoa's 2 bps fee, that minOut reflects the slippage setting, and that price impact and venue list are returned. It does not discuss quote staleness, rate limits, or whether quoting incurs cost, which keeps it below a 5.

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?

A single tightly-packed sentence that front-loads the core behavior and return shape, with no filler. The trailing 'Read-only.' fragment is slightly redundant given the annotations, but it is short and harmless.

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?

With no output schema, the description carries the burden of describing the response and does so by naming all four returned values including the fee treatment. Combined with a fully documented input schema and annotations, an agent has everything needed to call and interpret this tool.

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 all five parameters (chain default, amount in smallest unit with a wei example, native-token sentinel, slippageBps default/range) are already documented in structured data. The description adds only the linkage between slippage and the returned minOut, which is a marginal increment. Baseline 3 applies.

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 ('Compare every venue Stoa routes... return the route it would fill') and enumerates the returned fields (amountOut, minOut, price impact, venues), which makes clear this is a pricing simulation, not an execution. It does not name the sibling that executes (build_swap) or the cross-chain alternative (bridge_quote), so sibling differentiation is left implicit.

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 phrase 'return the route it would fill' and the trailing 'Read-only' imply this is the pre-trade preview step, but there is no explicit when-to-use statement, no exclusion against bridge_quote, and no stated ordering relative to build_swap. Usage is inferable but not directed.

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.