whale-data

What is developing

situations

Read-onlyIdempotent

What is going on right now, in stages (emerging, confirmed, escalating, cooling, contested): one coin, one story each, with the evidence behind it 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 50; 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.
`include_resolved`	No	Also finished ones with their outcome (Pro).

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.

Changed27 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: -"One coin symbol to filter to. Omit for every coin."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 / include_resolved / description

Previous value: -"Also return situations that resolved in the last 48h, with their outcomes. Pro and up."New value: +"Also finished ones with their outcome (Pro)."

addedInput schema / properties / limit

Added value: +{
+  "description": "Rows to return (usually up to 50; more is clamped and said).",
+  "type": "integer"
+}

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."
+}

removedOutput schema / properties / active_total

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Live situations before the free cap."
-}

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 / resolved

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Pro and up, when include_resolved: situations resolved in the last 48h with outcomes."
-}

removedOutput schema / properties / situations

Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "id, coin, type, type_label, direction, stage, headline, extreme, started_at, last_material_at, price_move_pct, families, supporting, conflicting, changes."
-}

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."

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 something was withheld: the cheapest plan that lifts it."
-}

removedOutput schema / properties / withheld

Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Live situations held back on this plan."
-}

AddedSep 5, 2026

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, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds context about the output structure (stages, evidence, price move) which is useful behavioral detail. However, it doesn't disclose any additional behaviors like pagination limits, rate limits, or specific handling of edge cases. Given the annotations, a 3 is appropriate.

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, front-loaded sentence that efficiently conveys the purpose and key output elements. It includes the stages, the 'one coin, one story' format, evidence, and price move without redundancy. It could arguably be slightly more structured (e.g., listing the parameters) but is concise and to the point.

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?

The description covers the core purpose and output format. An output schema exists, so return values are documented there. The parameter schema is complete. The description does not explicitly mention pagination, but the 'detail' and 'cursor' parameters imply it. Overall, it is sufficient for an agent to understand what the tool does and how to invoke it, though it could add a note on when to use 'full' vs 'brief'.

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%, meaning all five parameters are documented in the input schema. The description does not add any parameter-specific meaning beyond what the schema already provides. It mentions the stages but not how parameters like 'coin' or 'limit' map to the output. This matches the baseline of 3 when the schema handles the heavy lifting.

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 clearly states what the tool does: it provides a snapshot of current situations categorized by stages (emerging, confirmed, escalating, cooling, contested), with one coin and story each, including evidence and price move. This is specific about the resource and output format, though it lacks an explicit verb like 'list' or 'get'. It is distinct from siblings like 'market_now' or 'signals' in that it focuses on stage-based situation tracking, but it doesn't explicitly differentiate itself.

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 its use case (monitoring current developments) but provides no explicit guidance on when to use it versus alternatives, nor any exclusions. There is no mention of alternative tools or conditions that would favor another tool. The context is clear enough that an agent could infer usage, but it lacks direct routing information.

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?