Skip to main content
Glama

AINDEX

Stock tokens: Robinhood's feed against the on-chain price

get_stock_quotes
Read-only

For up to 16 Robinhood stock tokens: Robinhood's live feed per token (bid, ask, spread, day's range), the stock's last regular and extended-hours trades, the token's deepest on-chain pool, and chainPremium, how far the pool sits above or below the feed's midpoint. Off hours a gap larger than the full cost of a trade may be worth taking.

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": {
      "tokens": "<tokens>"
    },
    "name": "get_stock_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYes

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 adds real value beyond them by disclosing the 16-token batch ceiling and the exact shape of each per-token result, plus the semantic meaning of chainPremium relative to the feed midpoint.

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?

Two sentences, both earning their place: the first front-loads scope and return contents, the second gives interpretive guidance. Dense but readable, with no filler or repetition of the title.

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?

There is no output schema, so the description carries the full burden of describing return values and it does so field by field, including the non-obvious chainPremium metric. Combined with annotations covering safety and open-world access, an agent has everything needed to call this correctly.

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 0% for the single `tokens` array, so the description must carry the load. It does partially: it identifies the entries as Robinhood stock tokens and restates the 16-item limit, which tells the agent which addresses are valid. It does not clarify the required 0x address format, but with only one parameter the gap is modest.

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?

The description names a specific resource (Robinhood stock token quotes) and enumerates exactly what comes back: feed bid/ask/spread/day range, last regular and extended-hours trades, deepest on-chain pool, and chainPremium. It is unambiguous what the tool does, though it never contrasts itself with lookalike siblings such as get_token_market or get_candles.

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 closing sentence about off-hours gaps exceeding the round-trip cost implies the intended use case (spotting a tradable premium between pool and feed), which is useful implied guidance. However, it never states when to prefer this tool over the sibling market-data tools, nor any precondition such as requiring a connected account.

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.

Resources