whale-data

Cross-market screener

market_screener

Read-onlyIdempotent

Screen every recorded pair in one call: filter by funding_band / oi_band (vs each pair's OWN recorded days: record high, top 5%, top 25%, typical, bottom 25%, bottom 5%, record low), minimum whale-flow multiple vs the coin's own average, and radar-unusual. The discovery call. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max rows returned. Defaults to 20, hard ceiling 50 for everyone and no plan raises it. `matched` counts every pair that passed the filters regardless, and truncated says whether the rows are a shortened list.
`compact`	No	Return one plain-text line per matching pair rather than the JSON rows. Defaults to false.
`oi_band`	No	Same values as funding_band.
`funding_band`	No	One of: record high, top 5%, top 25%, typical, bottom 25%, bottom 5%, record low.
`unusual_only`	No	Keep only coins the radar currently marks unusual in its 1h, 4h or 24h window. Defaults to false.
`whale_mult_min`	No	Keep only coins whose 24h whale flow is at least this multiple of their own logged daily average, for example 3 for 3x and up. Coins with no logged multiple are dropped rather than treated as zero. Omit for no flow filter.

Output Schema

TableJSON Schema

Name	Required	Description
`line`	No	One plain-text line per matching pair, returned only when compact:true was asked for.
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`rows`	No	One row per matching pair: pair, coin, price, 24h change, the funding and open interest bands against the same pair recorded days with the day counts behind them, the whale multiple, and whether the ranking currently calls it unusual.
`capped`	No	Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit.
`compact`	No	Present and true only on a compact:true call, where the whole answer is the text in `line`.
`matched`	No	How many pairs passed every filter, counted before the row cap. Null when nothing was screened.
`criteria`	No	The filters as they were actually applied, so a misread argument is visible.
`returned`	No	How many rows are in this reply.
`available`	No	False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
`truncated`	No	True when more rows matched than were returned, so what you have is a page and not the whole set.
`access_note`	No	What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
`valid_bands`	No	The bands that do exist, returned alongside unknown_band.
`unknown_band`	No	Set when a band was named that this screen does not know. Nothing was screened, so this is not no matches.
`scanned_pairs`	No	How many pairs were examined.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedAug 13, 2026

addedInput schema / properties / compact / description

Added value: +"Return one plain-text line per matching pair rather than the JSON rows. Defaults to false."

addedInput schema / properties / limit / description

Added value: +"Max rows returned. Defaults to 20, hard ceiling 50 for everyone and no plan raises it. `matched` counts every pair that passed the filters regardless, and truncated says whether the rows are a shortened list."

addedInput schema / properties / unusual_only / description

Added value: +"Keep only coins the radar currently marks unusual in its 1h, 4h or 24h window. Defaults to false."

addedInput schema / properties / whale_mult_min / description

Added value: +"Keep only coins whose 24h whale flow is at least this multiple of their own logged daily average, for example 3 for 3x and up. Coins with no logged multiple are dropped rather than treated as zero. Omit for no flow filter."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "access_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears."
+    },
+    "available": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess."
+    },
+    "capped": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "applied": {
+              "description": "The value actually used.",
+              "type": "number"
+            },
+            "argument": {
+              "description": "Which argument was cut down, for example limit or hours.",
+              "type": "string"
+            },
+            "by": {
+              "description": "Why it was cut: keyless for the free ceiling, plan_max for a paid ceiling, tool_max for a ceiling no plan raises.",
+              "type": "string"
+            },
+            "max": {
+              "description": "The ceiling that applied.",
+              "type": "number"
+            },
+            "requested": {
+              "description": "The value the caller asked for.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "argument",
+            "requested",
+            "applied",
+            "max",
+            "by"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit."
+    },
+    "compact": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present and true only on a compact:true call, where the whole answer is the text in `line`."
+    },
+    "criteria": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The filters as they were actually applied, so a misread argument is visible."
+    },
+    "line": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One plain-text line per matching pair, returned only when compact:true was asked for."
+    },
+    "matched": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many pairs passed every filter, counted before the row cap. Null when nothing was screened."
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading."
+    },
+    "returned": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many rows are in this reply."
+    },
+    "rows": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One row per matching pair: pair, coin, price, 24h change, the funding and open interest bands against the same pair recorded days with the day counts behind them, the whale multiple, and whether the ranking currently calls it unusual."
+    },
+    "scanned_pairs": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many pairs were examined."
+    },
+    "truncated": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "True when more rows matched than were returned, so what you have is a page and not the whole set."
+    },
+    "unknown_band": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Set when a band was named that this screen does not know. Nothing was screened, so this is not no matches."
+    },
+    "valid_bands": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The bands that do exist, returned alongside unknown_band."
+    }
+  },
+  "type": "object"
+}

First observedAug 13, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is established. The description adds the key behavioral nuance that band comparisons are 'vs each pair's OWN recorded days' and that the whale-flow multiple is relative to the coin's own average, which is useful context beyond the annotations. However, it doesn't describe pagination, rate limits, or exact output behavior beyond what schema/output schema already provide.

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 dense two-sentence structure that front-loads the core action ('Screen every recorded pair') and then lists filters. It earns its length by conveying the discovery call scope and relative-band logic, though the parenthetical enumeration of band values (record high, top 5%, etc.) duplicates schema content and could be shortened without losing value.

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

Completeness5/5

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

The tool has 6 parameters, no required ones, full schema coverage, an output schema, and clear read-only annotations. The description supplies the missing high-level context: this is the cross-market discovery screen ('every recorded pair in one call') and filters are self-relative. It is complete enough for an agent to decide when to invoke and what to expect, without needing to explain return values due to the output schema.

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?

All 6 parameters have complete, detailed descriptions in the schema (100% coverage), so the description does not need to compensate. The description reiterates filter concepts like 'funding_band / oi_band' and 'whale_mult_min' but adds no new parameter-level meaning beyond summarizing what the schema already documents. Baseline 3 is appropriate.

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 opens with 'Screen every recorded pair in one call', giving a specific verb, resource, and scope. It then enumerates the filtering dimensions (funding/oi bands, whale-flow multiple, radar-unusual) and ends with 'The discovery call. Descriptive market data only.', which distinguishes it from other market tools like market_snapshot or whale_trades.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'The discovery call' clearly signals when to use this tool: when exploring across all recorded pairs. It also notes 'Descriptive market data only', excluding trade execution or data modification. However, it stops short of explicitly naming alternatives for different use cases (e.g., 'for pair-specific data use market_snapshot'), so it lacks formal exclusion guidance.

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?