whale-data

Live whale setups

big_catch

Read-onlyIdempotent

The whale-flow setups tracked right now, one coin each, with state (forming, confirmed, accelerating), direction, age and the price move since it started.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Coin symbol, e.g. BTC. A pair like ETH/USD works too.
`limit`	No	Rows to return (usually up to 100; more is clamped and said).
`cursor`	No	Next page: the cursor from the previous answer.
`detail`	No	brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	No	Data time, ISO.
`caveat`	No	A real limit, when non-null.
`cursor`	No	Next page (detail full).
`delayed`	No	Set when not live.
`summary`	No	The answer in one sentence.
`as_of_ms`	No	Data time, Unix ms.
`available`	No	False: no data; note says why.
`truncated`	No	Rows held back; see trimmed.
`next_tools`	No	Follow-up calls {tool,args,why}.
`access_note`	No	What this connection could not return.

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedSep 24, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +{}
```

changedInput schema / properties / coin / description

Previous value: -"Only the setup on this coin. Omit for every live setup."New value: +"Coin symbol, e.g. BTC. A pair like ETH/USD works too."

addedInput schema / properties / cursor

Added value: +{
+  "description": "Next page: the cursor from the previous answer.",
+  "type": "string"
+}

addedInput schema / properties / detail

Added value: +{
+  "description": "brief (default): the answer, key numbers and top rows. full: every row, paged with cursor.",
+  "enum": [
+    "brief",
+    "full"
+  ],
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Max setups. Defaults to 10, hard ceiling 50 for everyone."New value: +"Rows to return (usually up to 100; more is clamped and said)."

removedInput schema / properties / limit / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / limit / minimum
```
Removed value: --9007199254740991
```

removedInput schema / properties / pair

Removed value: -{
-  "description": "Alias for coin.",
-  "type": "string"
-}

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedOutput schema / properties / access_note

Added value: +{
+  "description": "What this connection could not return."
+}

addedOutput schema / properties / as_of

Added value: +{
+  "description": "Data time, ISO."
+}

addedOutput schema / properties / as_of_ms

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Data time, Unix ms."
+}

removedOutput schema / properties / available / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

changedOutput schema / properties / available / description

Previous value: -"False when the engine has not published (building:true)."New value: +"False: no data; note says why."

addedOutput schema / properties / available / type
```
Added value: +"boolean"
```

addedOutput schema / properties / caveat

Added value: +{
+  "description": "A real limit, when non-null."
+}

removedOutput schema / properties / count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Rows returned."
-}

addedOutput schema / properties / cursor

Added value: +{
+  "description": "Next page (detail full)."
+}

addedOutput schema / properties / delayed

Added value: +{
+  "description": "Set when not live."
+}

addedOutput schema / properties / next_tools

Added value: +{
+  "description": "Follow-up calls {tool,args,why}.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / setups

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "coin, state, tier, direction, direction_label, catch_type, severity, age_minutes, price_move_pct; Starter and up adds score, max_score, breakdown, fire_price, price."
-}

changedOutput schema / properties / summary / description

Previous value: -"The answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise."New value: +"The answer in one sentence."

removedOutput schema / properties / total

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Live setups matching the filter."
-}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Rows held back; see trimmed."
+}

removedOutput schema / properties / upgrade

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Present only when the score layer was withheld."
-}

AddedSep 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are live ('right now') and that detail can be brief or full, but it does not disclose clamping behavior or pagination details beyond what the schema already says. No contradiction with annotations.

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?

The description is a single, compact sentence that front-loads the core purpose and lists the key output fields. It is efficient and easy to scan, though it could be slightly more explicit about usage boundaries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety, the description is adequate for a read-only list tool. However, it does not clarify how this tool differs from whale_activity or whale_radar, and it leaves the agent to infer when to use it. For a tool with 4 optional parameters and a paging mechanism, a bit more context would help.

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 100%, so the schema already documents all four parameters. The description adds minimal semantic value beyond the schema, only reinforcing that the tool is live and that detail controls row granularity. Baseline 3 is appropriate.

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 states a specific verb ('tracked right now') and resource ('whale-flow setups'), and lists the key fields (state, direction, age, price move). It is clear what the tool returns, though it does not explicitly distinguish it from sibling tools like whale_activity or whale_radar.

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 description implies real-time tracking ('right now') and mentions optional filtering by coin and pagination via cursor, but it does not explicitly state when to use this tool versus alternatives like whale_activity or whale_radar. The usage context is implied rather than spelled out.

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

All whale-data 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.

Resources

Need Help?