Agent Einstein — Crypto & Market Intelligence

Robinhood Chain Whale Prints

get_robinhood_whale_prints

Read-onlyIdempotent

Individual large DEX trades on Robinhood Chain (EVM 4663) — the tokenized equities (NVDA, SPY, HIMS) and Pons memecoin flow that no mainnet whale feed carries, each with its token, side, venue and USD value. Every print is valued through its USDG or ETH leg and cross-checked, so trades priced off a freshly-created pool (which the raw chain data reports in the hundreds of millions) are excluded rather than published. WETH/USDG FX swaps are counted separately instead of dominating the tape.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return (1-25).

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Row cap applied to every list in this payload.
`prints`	No	The tape and the pass that produced it.
`reason`	No	Why the payload is absent, when `available` is false.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.
`fetchedAt`	No	When the underlying snapshot was refreshed (epoch ms or ISO-8601). Age matters: these are cached reads, not live queries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / properties / fetchedAt / description

Previous value: -"When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."New value: +"When the underlying snapshot was refreshed (epoch ms or ISO-8601). Age matters: these are cached reads, not live queries."

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "fetchedAt": {
+      "description": "When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."
+    },
+    "limit": {
+      "description": "Row cap applied to every list in this payload.",
+      "type": "number"
+    },
+    "prints": {
+      "additionalProperties": true,
+      "description": "The tape and the pass that produced it.",
+      "properties": {
+        "available": {
+          "description": "False when the last pass could not measure the chain."
+        },
+        "chain": {
+          "description": "Chain name."
+        },
+        "chainId": {
+          "description": "EVM chain id — 4663 for Robinhood Chain."
+        },
+        "ethSource": {
+          "description": "Where that ETH price came from."
+        },
+        "ethUsd": {
+          "description": "ETH price used to value the ETH-legged prints."
+        },
+        "minUsd": {
+          "description": "USD floor a trade had to clear to be printed."
+        },
+        "prints": {
+          "description": "Individual large trades.",
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "side": {
+                "description": "buy or sell."
+              },
+              "token": {
+                "description": "Token traded."
+              },
+              "usd": {
+                "description": "USD value of the print."
+              },
+              "venue": {
+                "description": "Pool or venue the print hit."
+              }
+            }
+          },
+          "type": "array"
+        },
+        "quoteSwapUsd": {
+          "description": "USD volume of those FX swaps."
+        },
+        "quoteSwaps": {
+          "description": "WETH/USDG FX swaps, counted separately so they do not dominate the tape."
+        },
+        "rowsRejected": {
+          "description": "Trades dropped as mispriced — a fresh pool reports values in the hundreds of millions, so they are excluded rather than published."
+        },
+        "rowsScanned": {
+          "description": "Trades examined."
+        },
+        "windowMinutes": {
+          "description": "Lookback window."
+        }
+      }
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedAug 31, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavioral context beyond them: how prints are valued (via USDG or ETH leg), the exclusion rule for freshly-created pools that would report inflated hundreds-of-millions figures, and the decision to count WETH/USDG FX swaps separately. These are non-obvious data-hygiene traits an agent could not derive from the schema.

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?

Front-loaded with what the tool returns, and each clause carries real information rather than filler. It is dense and the second sentence's parentheticals are heavy, but nothing is redundant with the schema or annotations.

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?

An output schema exists so return values need no explanation, and the description covers scope, valuation, and filtering thoroughly. The one material gap is the time window — it never says how recent the prints are or how they are ordered, which matters for a 'latest large trades' feed.

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?

Only one parameter (limit) with 100% schema description coverage, so the schema fully documents it including the 1-25 range and default of 10. The description adds no parameter meaning; baseline 3 is appropriate when the schema carries the load.

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?

States a specific verb+resource ('Individual large DEX trades on Robinhood Chain') with the exact chain identifier (EVM 4663), the asset classes covered (tokenized equities like NVDA/SPY/HIMS and Pons memecoins), and the fields each print carries. The phrase 'that no mainnet whale feed carries' effectively distinguishes it from the many whale/flow siblings (track_whales, get_hyperliquid_whales, get_smart_money_flow) without needing to name them.

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?

Usage context is implied by the framing ('the flow that no mainnet whale feed carries') and by the exclusions described, but there is no explicit when-to-use statement or named alternative among the 30+ siblings. An agent can infer it is for Robinhood-chain whale flow, but must guess whether to prefer it over get_hyperliquid_whales or track_whales for a given query.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Einstein — Crypto & Market Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.