Skip to main content
Glama

Stoa: swaps on Robinhood Chain

Robinhood stock tokens

stock_tokens
Read-only

Robinhood Stock Tokens on Robinhood Chain: Robinhood's price for the underlying stock next to the on-chain price, liquidity, 24h volume and whether Stoa can route a swap. Optionally filter by ticker.

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": "stock_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoOptional ticker, e.g. NVDA.
routableOnlyNoOnly stocks Stoa can swap right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only and open-world. Beyond that, the description discloses the returned data dimensions (underlying vs on-chain price, liquidity, volume, routability) and the optional ticker filter, though it omits ordering, pagination, and empty-result behavior.

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?

Single front-loaded sentence that begins with the resource and then lists the data fields; there is little wasted wording. The only mild redundancy is repeating the tool/title scope, but it anchors the chain context.

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?

No output schema exists, so the description must carry return-value context; it does so by naming the price, liquidity, volume, and routability fields. It does not cover pagination/order or max results, so completeness is good but not exhaustive.

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 both symbol and routableOnly are already documented. The description reinforces the symbol filter ('Optionally filter by ticker') but adds no format, matching, or precedence details beyond 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 the specific resource (Robinhood Stock Tokens on Robinhood Chain) and enumerates the returned fields: underlying stock price, on-chain price, liquidity, 24h volume, and Stoa routability. It is clear enough to distinguish from quote/build_swap siblings, though it does not explicitly name an alternative.

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 only usage cue is 'Optionally filter by ticker' and the schema's routableOnly flag; there is no explicit when-to-use, when-not-to-use, or sibling alternative guidance. The intent is inferable, but routing between this and quote/market_context is left to the agent.

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.