Skip to main content
Glama

whale-insights

by com.cryptowhaleinsights
OverviewDiscussionsAdmin

analysts_signals

Read-onlyIdempotent

Analyst signal history — single or multi-analyst (public, free-tier, MCP-compatible) — Returns the last 7 days of signals for one or more analysts in a single request. Pass a single id (e.g. ?id=chain_hawk) for one analyst or a comma-separated list (e.g. ?id=chain_hawk,whale_watch) to compare multiple analysts without extra round-trips. Analyst ids: chain_hawk (ChainHawk, BTC & macro), whale_watch (WhaleWatch, multi-chain whales), alpha_scout (AlphaScout, emerging tokens), defi_pulse (DeFiPulse, DeFi/stables/bridges), quant_edge (QuantEdge, signal risk/convergence). Always free-tier depth (last 7 days, up to 200 signals per analyst). No authentication required. Single-id response: { analystId, tier, signals[], updatedAt }. Multi-id response (comma-separated): { results: { [analystId]: signals[] }, tier, updatedAt }. To fetch all 10 analysts at once, use GET /api/public/analysts/signals/all. Each signal: id (number), tokens (array), typeLabel, outcome ('win'|'loss'|null), returnPct (null if unresolved), create

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAnalyst slug(s). Single: chain_hawk. Comma-separated for multi: chain_hawk,whale_watch. Valid values: chain_hawk, whale_watch, alpha_scout, defi_pulse, quant_edge.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoAlways 'free' for this public endpoint
resultsNoPresent in multi-id mode. Keys are analyst slugs; values are arrays of signal objects.
signalsNoPresent in single-id mode. Array of signal objects for the requested analyst.
analystIdNoEchoed analyst slug (single-id mode only), e.g. chain_hawk
updatedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "analystId": {
+      "description": "Echoed analyst slug (single-id mode only), e.g. chain_hawk",
+      "type": "string"
+    },
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "results": {
+      "additionalProperties": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "description": "Present in multi-id mode. Keys are analyst slugs; values are arrays of signal objects.",
+      "type": "object"
+    },
+    "signals": {
+      "description": "Present in single-id mode. Array of signal objects for the requested analyst.",
+      "items": {
+        "properties": {
+          "analystId": {
+            "description": "Analyst slug",
+            "type": "string"
+          },
+          "createdAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "id": {
+            "description": "Unique signal row ID",
+            "type": "number"
+          },
+          "outcome": {
+            "description": "'win' | 'loss' | null if unresolved",
+            "nullable": true,
+            "type": "string"
+          },
+          "returnPct": {
+            "description": "Pct-point return, e.g. 8.4 = +8.4%. Null if unresolved.",
+            "nullable": true,
+            "type": "number"
+          },
+          "tokens": {
+            "description": "Symbols involved, e.g. ['BTC']",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "typeLabel": {
+            "description": "Human-readable signal type, e.g. 'Whale Move', 'Volume Breakout'",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tier": {
+      "description": "Always 'free' for this public endpoint",
+      "type": "string"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark the tool as read-only/idempotent/non-destructive, and the description adds valuable behavioral context: free-tier depth, the 7-day window, the 200-signal cap per analyst, no authentication requirement, and the exact response shapes for both single- and multi-id calls. It clearly discloses limits and output behavior beyond the structured annotations.

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 organized around distinct pieces of information: usage, analyst IDs, limits, authentication, and response formats. The core purpose is front-loaded, and most sentences earn their place, though the inclusion of full response shapes and signal field listings makes it denser than strictly necessary.

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?

For a one-parameter read-only tool with an output schema, the description is remarkably complete: it covers single vs multi behavior, the all-analysts alternative, data depth limits, auth expectations, and response structures. An agent has everything needed to invoke it correctly without opening the schema.

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 schema already describes id as an analyst slug and lists valid values, yielding 100% schema coverage, so the baseline is 3. The description adds extra meaning by explaining comma-separated multi-analyst usage, providing concrete URL examples, and mapping each slug to a human-readable analyst and focus area, which improves parameter understanding without redundancy.

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 object ('Analyst signal history') and a clear action ('Returns the last 7 days of signals'), then states both single- and multi-analyst modes. It also names the sibling endpoint for fetching all analysts at once, so an agent can distinguish it from analysts_signals_all without inferring.

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?

It explicitly tells the agent when to use a single id versus a comma-separated list, notes that multi-id avoids extra round-trips, and directs the agent to the /all endpoint for fetching all 10 analysts. This provides actionable selection criteria, including the key alternative.

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

All whale-insights 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