Skip to main content
Glama

AINDEX

Robinhood Chain signals

rh_signals
Read-only

Data no general crypto service has, by view. premium: each stock token's DEX vs Chainlink vs Lighter perp vs Robinhood feed price and gaps, with history for up to 4 tokens. deployer: a token's or pool's deployer and how their other tokens ended. dividends: multiplier steps vs real cash dividends. smart_money: wallets by realised profit on the top tokens and what they bought. listings: new Robinhood stock tokens and Lighter markets. filings: 8-Ks and insider cluster buys where the token or perp has not moved since. unlocks: scheduled token unlocks (DefiLlama), cliff or linear, as a percent of circulating supply, from 3 days back (a short into an unlock holds until a day after) to days ahead; ticker is the coin.

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": {
      "view": "<view>"
    },
    "name": "rh_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
poolNo
viewYes
limitNo
tokenNo
tickerNo
tokensNo
gapsOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data scope are covered. The description adds useful behavioral constraints beyond that: history limited to up to 4 tokens, unlocks sourced from DefiLlama with a window starting 3 days back, and the note that ticker refers to the coin rather than the stock. It says nothing about cost, rate limits, or the shape/size of the response for a tool that fans out to seven very different datasets.

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?

It is front-loaded with the view idea and then structured as a view-by-view list, which is an efficient shape for a seven-mode tool. The prose is telegraphic and occasionally overloaded (the unlocks sentence nests source, cadence, window, and ticker semantics in one clause), but no sentence is padding.

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?

Given eight parameters, seven distinct views, no output schema, and no schema descriptions, the description supplies enough per-view content and key constraints (token cap, unlock window, ticker meaning) for correct invocation. What remains thin is the interaction between shared parameters (days, limit) and the views, which the agent must guess.

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 0%, so the description carries the parameter burden, and it does explain the enum members in detail plus the ticker convention and the 4-token cap on premium history. However, days, limit, gapsOnly, pool, and token are never mentioned, so an agent cannot tell what days means outside the unlocks view or what gapsOnly filters.

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 the resource (Robinhood Chain signals) and then enumerates all seven view values with what each one returns (price gaps across DEX/Chainlink/Lighter/Robinhood, deployer history, dividend multipliers, smart-money wallets, listings, filings, unlocks). This is far more specific than a generic 'get signals' tool, and an agent can pick a view from the text alone. It stops short of a clean verb framing ('Data no general crypto service has, by view') and never says it is a single call dispatched by the view parameter.

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?

Implicit guidance exists: each view is described with the question it answers, so an agent can map an intent to a view. There is no explicit when-to-use versus named siblings such as get_dividends, discover_tokens, get_token_market, or get_lighter_markets, and no statement of when this tool is the wrong choice.

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