Skip to main content
Glama

whale-data

by com.coinlobster
OverviewDiscussionsAdmin

One-call market brief

market_brief
Read-onlyIdempotent

The complete current answer for ONE coin in a single call, in causal order: what the price did, what the headlines say (summary, mood score, recent headlines), what whale flow did against the coin's own baseline, what was forced out, and what holding it costs (cross-venue funding with carry, open interest, historical context). The plain-English name for trade_context (identical data and credit cost). THIS is the tool for "why is BTC pumping", "why is ETH moving", "what is driving this", "what is happening with SOL": the news is already inside it, so do not follow up with crypto_news, nor with the separate whale, funding or liquidation tools, unless the user drills into one of them. Descriptive market data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoAlias for pair.
pairNoTrading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. On the free plans BTC answers in full and any other coin as a headline.
compactNoReturn one line of plain text rather than the JSON blob, about 30 tokens instead of 800. Same facts, same windows, same dates, no structured fields to read. Defaults to false.
position_usdNoPosition size in US dollars, for example 25000. Above zero only. When given, carry_cost adds per_day_usd_at_current_rate, the dollars a day the current funding average across exchanges works out to at that size. Arithmetic on the rate as it stands now, not a projection of future rates. Omit and carry_cost still carries the percentage and APR figures.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineNoThe composed one-line answer, returned only when compact:true was asked for. The same facts, the same windows and the same dates as the full shape.
newsNoWhat is being said about this coin, so a "why is it moving" question is answered in this one call: summary (the written one-liner), sentiment and sentiment_score (minus 100 to plus 100, NULL when nothing was recorded, which is not the same as neutral), points (the written points behind the summary, each with a kind), key_level, headlines (title, source, published, link) and macro (the same read for the market as a whole). available:false with covered:true means the coin is recorded and this plan reaches BTC and macro only.
noteNoOne line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
pairNoThe pair this context describes.
depthNoWhich shape came back: lite, free-pair or keyed.
priceNoLast traded price.
compactNoPresent and true only on a compact:true call, where the whole answer is the single line in `line`.
fundingNoaverage_rate across exchanges, how many exchanges are in it, the interval in hours, and minutes to the next funding time.
crowdingNoThe crowding read and the overexposed side. Null without a paid plan.
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.
stats_24hNoThe 24h statistics block. Absent on the lite shape, where locked_layers names it.
carry_costNoArithmetic on the current funding average: percent per day, the same as an annual rate, which side pays, and dollars a day when position_usd was passed. Not a projection of future rates.
whale_flowNoWhale direction against the same coin logged baseline: the multiple, days logged, record and N-day-high flags, and buy share now versus 7 days. Dollar sizes are added on a paid plan.
price_readsNoPlain descriptions of price against its own recent hours, computed from hourly candles: vs_recent_average (above or below its 50-hour and 200-hour average, and which way it is drifting), recent_move (how stretched the latest move is, plus the change against 7 days ago) and choppiness (calm, normal or choppy). Each block is available:true with values or available:false with a plain reason; a leg with too few recorded hours is null with a note, never a made-up neutral. Descriptive, not a trade signal.
locked_layersNoNamed rather than silently missing: which blocks this connection did not receive.
vs_own_historyNoWhere funding and open interest sit against the same pair recorded days: phrase, band, day count, the date the reading is from, and how past cases resolved.
open_interest_usdNoOpen interest in dollars across the exchanges that publish it.
liquidations_recentNoForced closes visible right now: count, long_usd, short_usd and window_minutes. A timing series, market-wide totals run higher.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / news
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "What is being said about this coin, so a \"why is it moving\" question is answered in this one call: summary (the written one-liner), sentiment and sentiment_score (minus 100 to plus 100, NULL when nothing was recorded, which is not the same as neutral), points (the written points behind the summary, each with a kind), key_level, headlines (title, source, published, link) and macro (the same read for the market as a whole). available:false with covered:true means the coin is recorded and this plan reaches BTC and macro only."
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / pair / description
      Previous value: -"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Any streamed pair answers keyless; off the free pairs a keyless reply is the lite shape and names what it withheld in locked_layers."New value: +"Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. On the free plans BTC answers in full and any other coin as a headline."
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds context by stating 'Descriptive market data only'. It also discloses the free-plan limitation (full BTC answers vs. headline-only for other coins) and the identical data/credit cost to trade_context, which are valuable beyond the annotations. No contradictions.

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 long but front-loaded with the core purpose and example queries. Each sentence adds meaningful information—scope, components, usage examples, exclusions, and additional behavioral notes. Slightly verbose but earned, not padded.

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?

Despite having an output schema, the description explains the causal order and typical use cases, names alternatives, provides exclusions, and covers parameter nuances (free plan, compact mode). It leaves nothing an agent needs to call it correctly, and the output schema handles return details.

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 fully documents all four parameters. The description does not add semantic details beyond the schema, though it does restate that 'coin' is an alias for 'pair' and mentions the compact option. Baseline 3 is appropriate since the schema carries the weight.

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 it provides the complete current answer for ONE coin, listing specific components (price, news, whale flow, funding, etc.) and explicitly names the sibling tool trade_context as identical. It also gives concrete example queries ('why is BTC pumping'), making its purpose unmistakable and distinguishable from other tools.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance with example questions, and explicitly instructs the agent not to follow up with crypto_news or separate whale/funding/liquidation tools unless the user drills in. It also names the alternative trade_context, providing clear selection criteria.

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