Skip to main content
Glama

whale-data

by com.coinlobster
OverviewDiscussionsAdmin

My watchlist

watchlist_brief
Read-onlyIdempotent

Every coin on your watchlist through the whale read in one call: flow against each coin's normal, buy or sell lean, and whether it is unusual now. Needs a signed-in connection (free).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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. Changed19 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +{}
    • 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."
+}
    • 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 keyless (reason no_owner) or when the watchlist is empty (empty: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 / coins
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {},
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Per watchlist coin: the whale-context read (multiple vs average, records, buy share), direction, unusual_now, and the dollar flow on Starter and up."
-}
    • removedOutput schema / properties / count
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "number"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Coins read (up to 10)."
-}
    • 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 / radar
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The radar rows for these coins per window, in the same shape whale_radar returns on this plan."
-}
    • 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 on the free shape: the cheapest plan that adds the dollar flow."
-}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat those. It adds useful context beyond annotations: an authentication requirement and the kind of analytical output provided. No contradiction exists.

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 concise sentences with no filler. The primary purpose and output are front-loaded, and the auth note is brief but relevant.

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 description is complete for a zero-parameter read-only tool: it states what data is returned, the auth requirement, and the scope. The output schema covers return structure, and annotations cover the behavior profile, so nothing important is missing.

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

Parameters4/5

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

The tool has zero parameters and schema description coverage is 100%, so the schema fully documents the input surface. The description adds no parameter-specific meaning, but none is needed; the baseline for zero-parameter tools is 4.

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 the tool returns every coin on the user's watchlist with specific metrics: flow against normal, buy/sell lean, and unusualness. It names the resource (watchlist) and differentiates itself from sibling tools like 'watch' by focusing on a per-coin brief in one call.

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?

It gives a clear context: use this to get watchlist coins with whale-flow analysis in a single call. It also states the prerequisite of a signed-in connection. It does not explicitly name alternatives or when-not-to-use, but the context is strong enough for an agent to know when it applies.

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