Skip to main content
Glama

Stoa: swaps on Robinhood Chain

Build an unsigned swap

build_swap
Read-only

Same as quote, plus the unsigned transaction (to, data, value, chainId) for the taker's wallet to sign, and the approval it needs first when selling a token. Stoa never signs or sends anything.

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>",
      "taker": "<taker>"
    },
    "name": "build_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork. Default robinhood.
takerYesThe wallet that signs, pays and receives.
amountYesAmount to sell, integer in the sell token's smallest unit (wei).
buyTokenYesToken to buy: a token address, or "native" for the gas token (ETH on Robinhood Chain, HYPE on Elysium).
referrerNoOptional wallet that earns 10% of Stoa's fee on this swap.
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.
deadlineSecondsNoSeconds until the transaction expires. Default 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=true already supplied, the description adds real value by clarifying that the returned transaction is unsigned, that an approval must be sent first when selling a token, and that Stoa never signs or sends anything. That resolves the apparent tension between 'builds a transaction' and a readOnly annotation. It does not cover deadline or slippage behavior in the returned payload, so it is not exhaustive.

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?

Two short sentences, front-loaded with the differentiator ('Same as quote, plus...') and closed with the critical safety fact that Stoa never signs or sends. No filler or repetition of schema detail.

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 an eight-parameter tool with no output schema, the description compensates by sketching the returned transaction shape and flagging the approval step, which is what the agent most needs to know. It leaves the signing/broadcast handoff only implied, which is a minor remaining gap rather than a blocking one.

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% with all eight parameters documented, including defaults, enums, and the 'native' token convention, so the schema carries parameter meaning. The description adds nothing parameter-specific, which is the baseline 3 case.

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 verb and product: it builds an unsigned swap transaction, and it anchors that against the sibling 'quote' ('Same as quote, plus...'), so an agent knows exactly what extra this tool returns versus the quote tool. It also enumerates the transaction fields (to, data, value, chainId), which makes the output's purpose concrete.

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?

'Same as quote, plus the unsigned transaction ... for the taker's wallet to sign' implicitly tells the agent to choose this tool when it needs something signable rather than just a price. It does not explicitly state the inverse condition (use quote when no transaction is needed) or any prerequisite like wallet connection, so it stops short of full when/when-not guidance.

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.