Skip to main content
Glama

Whale flow by hour

whale_flow
Read-onlyIdempotent

Hourly buy and sell USD flow buckets for one coin, CEX and DEX split, over a rolling window. Descriptive market data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoCoin symbol, for example BTC. A pair like ETH/USD works too, the quote leg is dropped. Required: with nothing to look up the call is refused rather than answered about a different coin.
pairNoAlias for coin.
coinsNoPortfolio read: a list of coin symbols (or a comma-separated string) answered side by side in one call, up to 10. Omit for one coin.
hoursNoHow many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 24 on the free plans, 336 on Starter and 720 on Pro. Asking for more returns the cap, and the payload says so in `capped`.
detailNoExtra per-hour detail: venues adds the per-venue dollar split, wallets adds the wallets behind each hour, all adds both. Off by default (a week of wallet lists is large). Pro and up; below that the payload names the plan.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoThe coin these hours belong to.
noteNoOne line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
rowsNoOne row per recorded hour: the hour stamp, buy and sell dollars, and the CEX / on-chain / Hyperliquid split. The per-hour wallet list and per-exchange table are not carried here (see whale_profile and hl_whales for those); this tool is the hourly timeline.
countNoHow many hours carry a recorded reading. Fewer than hours means the rest were never recorded, not that they were quiet.
hoursNoHow many hours back were read.
cappedNoPresent 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.
summaryNoThe 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.
availableNoFalse 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.
depth_noteNoHow far back the data behind this answer reaches.
access_noteNoWhat this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hours / description
      Previous value: -"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 168 keyless, 336 on Starter and 720 on Pro. Asking for more returns the cap, and the payload says so in `capped`."New value: +"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 24 on the free plans, 336 on Starter and 720 on Pro. Asking for more returns the cap, and the payload says so in `capped`."
  2. Changed3 schema fields changed
    • addedInput schema / properties / coins
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Portfolio read: a list of coin symbols (or a comma-separated string) answered side by side in one call, up to 10. Omit for one coin."
      +}
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Extra per-hour detail: venues adds the per-venue dollar split, wallets adds the wallets behind each hour, all adds both. Off by default (a week of wallet lists is large). Pro and up; below that the payload names the plan.",
      +  "enum": [
      +    "none",
      +    "venues",
      +    "wallets",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / hours / description
      Previous value: -"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 168 keyless and 720 on a paid plan. Asking for more returns the cap, and the payload says so in `capped`."New value: +"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 168 keyless, 336 on Starter and 720 on Pro. Asking for more returns the cap, and the payload says so in `capped`."
  3. Changed1 schema field changed
    • changedInput schema / properties / hours / description
      Previous value: -"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 168 keyless and 720 on a developer plan. Asking for more returns the cap, and the payload says so in `capped`."New value: +"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 168 keyless and 720 on a paid plan. Asking for more returns the cap, and the payload says so in `capped`."
  4. Changed2 schema fields changed
    • changedOutput schema / properties / rows / description
      Previous value: -"One row per recorded hour: the hour stamp plus buy and sell dollars, split CEX and on-chain."New value: +"One row per recorded hour: the hour stamp, buy and sell dollars, and the CEX / on-chain / Hyperliquid split. The per-hour wallet list and per-exchange table are not carried here (see whale_profile and hl_whales for those); this tool is the hourly timeline."
    • addedOutput schema / properties / summary
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "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."
      +}
  5. Changed3 schema fields changed
    • addedInput schema / properties / coin / description
      Added value: +"Coin symbol, for example BTC. A pair like ETH/USD works too, the quote leg is dropped. Required: with nothing to look up the call is refused rather than answered about a different coin."
    • addedInput schema / properties / hours / description
      Added value: +"How many hours of hourly buckets to read back. Defaults to the whole window, which is also the ceiling: 168 keyless and 720 on a developer plan. Asking for more returns the cap, and the payload says so in `capped`."
    • 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."
      +    },
      +    "coin": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "The coin these hours belong to."
      +    },
      +    "count": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How many hours carry a recorded reading. Fewer than hours means the rest were never recorded, not that they were quiet."
      +    },
      +    "depth_note": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How far back the data behind this answer reaches."
      +    },
      +    "hours": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "How many hours back were read."
      +    },
      +    "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."
      +    },
      +    "rows": {
      +      "anyOf": [
      +        {
      +          "items": {},
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "One row per recorded hour: the hour stamp plus buy and sell dollars, split CEX and on-chain."
      +    }
      +  },
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds 'Descriptive market data only,' reinforcing non-actionability modern. It also mentions the rolling window, which is behavioral context not in annotations. However, it does not explicitly mention rate limits or that the tool refuses calls with no coin (though the schema does).

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?

Two sentences with zero waste. The core purpose is front-loaded: 'Hourly buy and sell USD flow buckets' immediately conveys the resource and time granularity. The sentence 'Descriptive market data only' adds essential behavioral context in a compact way. No filler or repetition.

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 an output schema (not provided), so return format is not needed. The description covers the core concept, scope (one coin, hourly, rolling window), and nature (descriptive). With annotations covering safety, the description is complete for an agent to select and invoke the tool correctly. The schema details handle everything else.

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 coverage is 100%, so all parameters are described in the schema itself. The description does not add meaning beyond the schema, but the schema descriptions are quite detailed (e.g., 'quote leg is dropped', 'Defaults to the whole window'). The description's 'CEX and DEX split' clarifies the output but not parameter semantics. Baseline 3 is appropriate because schema covers everything.

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 clearly states 'hourly buy and sell USD flow buckets for one coin, CEX and DEX split, over a rolling window.' This is a specific verb (read) plus resource (flow buckets) with clear scope (one coin, hourly, CEX/DEX split). It distinguishes itself from siblings like 'whale_trades' or 'whale_tape' by focusing on aggregated hourly flow rather than individual trades. The phrase 'Descriptive market data only' further clarifies its non-actionable nature.

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 description implies usage for when you need hourly buy/sell flow data for a single coin, which contrasts with siblings like 'whale_trades' (individual trades) or 'whale_tape' (tape data). However, it does not explicitly name alternatives or state when NOT to use it. The presence of a 'coins' parameter for portfolio read hints at a use case (multiple coins) but is not highlighted in the description. Clear enough context for an agent to infer appropriate use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources