Skip to main content
Glama

whale-data

by com.coinlobster
OverviewDiscussionsAdmin

Market screener

market_screener
Read-onlyIdempotent

Screen every recorded pair at once: funding_band and oi_band against each pair's own recorded days (record high, top 5%, top 25%, typical, bottom 25%, bottom 5%, record low), a minimum whale-flow multiple, and unusual-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return (usually up to 50; more is clamped and said).
cursorNoNext page: the cursor from the previous answer.
detailNobrief (default): the answer, key numbers and top rows. full: every row, paged with cursor.
compactNotrue: one line per coin.
oi_bandNoOpen interest band(s).
funding_bandNoFunding band(s), e.g. "top 5%".
unusual_onlyNoOnly coins with unusual whale activity now.
whale_mult_minNoMinimum whale flow as a multiple of the coin's own average.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoData time, ISO.
caveatNoA real limit, when non-null.
cursorNoNext page (detail full).
delayedNoSet when not live.
summaryNoThe answer in one sentence.
as_of_msNoData time, Unix ms.
availableNoFalse: no data; note says why.
truncatedNoRows held back; see trimmed.
next_toolsNoFollow-up calls {tool,args,why}.
access_noteNoWhat this connection could not return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed38 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +{}
    • changedInput schema / properties / compact / description
      Previous value: -"Return one plain-text line per matching pair rather than the JSON rows. Defaults to false."New value: +"true: one line per coin."
    • 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 / funding_band / description
      Previous value: -"One of: record high, top 5%, top 25%, typical, bottom 25%, bottom 5%, record low."New value: +"Funding band(s), e.g. \"top 5%\"."
    • changedInput schema / properties / limit / description
      Previous 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."New value: +"Rows to return (usually up to 50; more is clamped and said)."
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / limit / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / oi_band / description
      Previous value: -"Same values as funding_band."New value: +"Open interest band(s)."
    • changedInput schema / properties / unusual_only / description
      Previous value: -"Keep only coins the radar currently marks unusual in its 1h, 4h or 24h window. Defaults to false."New value: +"Only coins with unusual whale activity now."
    • changedInput schema / properties / whale_mult_min / description
      Previous 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."New value: +"Minimum whale flow as a multiple of the coin's own average."
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / properties / access_note / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedOutput schema / properties / access_note / description
      Previous value: -"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."New value: +"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 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."New value: +"False: no data; note says why."
    • addedOutput schema / properties / available / type
      Added value: +"boolean"
    • removedOutput schema / properties / capped
      Removed value: -{
-  "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."
-}
    • addedOutput schema / properties / caveat
      Added value: +{
+  "description": "A real limit, when non-null."
+}
    • removedOutput schema / properties / compact
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Present and true only on a compact:true call, where the whole answer is the text in `line`."
-}
    • removedOutput schema / properties / criteria
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The filters as they were actually applied, so a misread argument is visible."
-}
    • addedOutput schema / properties / cursor
      Added value: +{
+  "description": "Next page (detail full)."
+}
    • addedOutput schema / properties / delayed
      Added value: +{
+  "description": "Set when not live."
+}
    • removedOutput schema / properties / line
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "One plain-text line per matching pair, returned only when compact:true was asked for."
-}
    • removedOutput schema / properties / matched
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "How many pairs passed every filter, counted before the row cap. Null when nothing was screened."
-}
    • addedOutput schema / properties / next_tools
      Added value: +{
+  "description": "Follow-up calls {tool,args,why}.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / note
      Removed value: -{
-  "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."
-}
    • removedOutput schema / properties / returned
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "How many rows are in this reply."
-}
    • removedOutput schema / properties / rows
      Removed value: -{
-  "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."
-}
    • removedOutput schema / properties / scanned_pairs
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "How many pairs were examined."
-}
    • addedOutput schema / properties / summary
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The answer in one sentence."
+}
    • removedOutput schema / properties / truncated / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when more rows matched than were returned, so what you have is a page and not the whole set."New value: +"Rows held back; see trimmed."
    • removedOutput schema / properties / unknown_band
      Removed value: -{
-  "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."
-}
    • removedOutput schema / properties / valid_bands
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The bands that do exist, returned alongside unknown_band."
-}
  2. Changed5 schema fields changed
    • 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"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark this as read-only and idempotent.te, lowering the bar. The description adds meaningful behavioral context by stating that bands are evaluated 'against each pair's own recorded days' and by listing the exact band thresholds. This helps the agent understand that results are relative per pair, not global.

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?

The description is a single, front-loaded sentence: 'Screen every recorded pair at once' followed by a compact list of criteria. No filler or redundant phrases. The band list is dense but necessary, and each element earns its place.

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?

With an output schema present, the description doesn't need to cover return shapes. It fully explains the screening logic, the key parameter semantics, and the tool's scope. Pagination and output-detail parameters are already documented in the schema, so an agent has everything needed to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds crucial meaning beyond the schema: it explains that funding_band and oi_band are interpreted relative to each pair's own recorded days, and it clearly maps 'minimum whale-flow multiple' to whale_mult_min and 'unusual-only' to unusual_only. This resolves ambiguity that the bare schema leaves.

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 a specific verb and resource: 'Screen every recorded pair at once.' It then enumerates the screening criteria (funding_band, oi_band, whale-flow multiple, unusual-only), making it unmistakable what the tool does. This distinguishes it clearly from siblings like coin_brief or watchlist_brief, which target narrower scopes.

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 'every recorded pair at once' makes the tool's use case explicit: whole-market screening rather than single-coin or watchlist inspection. It doesn't name alternative tools or list exclusion conditions, but the context is clear enough for an agent to decide when to invoke it.

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

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