get_chain_stats
Latest Robinhood Chain stats: TVL, 24h DEX volume, stablecoin mcap, transactions today, total addresses.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
0xrhXBT — Robinhood Chain Intelligence
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It mentions 'Latest' but lacks details on data freshness, refresh rate, safety, or side effects. The tool is likely read-only, but this is not confirmed.
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?
One sentence, front-loaded with key information, zero waste. Perfectly concise for the simplicity of the tool.
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 no output schema, description lists exact metrics returned. For a zero-parameter tool, this is reasonably complete, though a hint about data structure or units would enhance usability.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist (baseline 4). Description adds meaning by listing the returned stats, which compensates for the lack of output schema.
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 clearly states the tool provides 'Latest Robinhood Chain stats' and lists specific metrics (TVL, 24h DEX volume, stablecoin mcap, transactions, total addresses), distinguishing it from sibling tools that focus on individual tokens or risk analysis.
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?
No explicit guidance on when to use this tool versus alternatives. For a zero-parameter tool, context is simple, but exclusions or comparisons to siblings like get_token or get_intel would improve clarity.
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.
TDQS
A3.7/5.0
Disambiguation5/5
Every tool targets a distinct slice of Robinhood Chain intelligence: token data, premiums, perp markets, stablecoin flows, corporate actions, risk checks, and sentiment. Even overlapping areas (e.g., get_token vs. search_tokens, get_stock_premiums vs. get_stock_multipliers) are clearly separated by purpose. No two tools appear to duplicate each other's core function.
Naming Consistency3/5
The tool names mix conventions: most are verb-led (get_, search_, check_), but several are noun phrases (chain_composition, perps_markets, stablecoin_flows). Within the get_ group the pattern is consistent, but across the full set the mixing of prefixes and bare nouns makes the naming less predictable. Still, each name is descriptive enough to infer its role at a glance.
Tool Count2/5
With 26 tools, the set exceeds the 25-tool threshold for 'too many'. While the domain is broad (covering tokens, perps, stablecoins, corporate actions, flows, and narratives), the sheer number risks over engineering and agent confusion. Some tools could be grouped (e.g., perps_funding and perps_markets might be one, get_token and get_token_candles might share). The scope feels stretched.
Completeness4/5
The surface covers a comprehensive array of Robinhood Chain data: token details, market premiums, perp funding, stablecoin flows, settlement graphs, corporate actions, and risk assessment. Minor gaps exist (e.g., no direct wallet transaction history, no governance queries), but for the stated purpose of 'chain intelligence' the coverage is robust and includes both live and historical reads.