whale-insights

golden_alerts_snapshot

Read-onlyIdempotent

Golden Alerts snapshot — latest market intelligence alerts (public, MCP-compatible) — Returns the latest snapshot of CryptoWhaleInsights Golden Alerts — up to 27 high-signal market alerts refreshed every 5 minutes by the platform's cron job. Each alert represents a confluence of whale on-chain activity, volume momentum, and Fear & Greed context. This endpoint reads directly from the in-process cache (no new AI query triggered per request). Pro-only fields (raw confidence score, internal factors, price targets, exit signals) are intentionally omitted; severity is mapped to low/medium/high for public consumption. Alert types: accumulation | fear_buy | smart_money_loading | volume_breakout | whale_convergence. Severity mapping: high (confidence ≥70%), medium (45–69%), low (<45%). Response: { alerts[], total, refreshedAt (ISO-8601 or null if cache empty), updatedAt }. Each alert: id, title, type, severity, tokens (string[]), chains (string[]), summary, aiInsight, analystId (string | null), createdAt. No authentic

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`total`	No	Number of alerts in the snapshot
`alerts`	No	Golden Alerts sorted by severity (highest first), up to 27 entries.
`updatedAt`	No	Response generation timestamp
`attribution`	No
`refreshedAt`	No	When the cron job last populated the cache; null if cache is empty

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "alerts": {
+      "description": "Golden Alerts sorted by severity (highest first), up to 27 entries.",
+      "items": {
+        "properties": {
+          "aiInsight": {
+            "description": "One-sentence AI-generated actionable insight",
+            "type": "string"
+          },
+          "analystId": {
+            "description": "Attributed analyst slug: chain_hawk | whale_watch | alpha_scout | defi_pulse | quant_edge | rate_hawk | flow_tracer | unlock_guard | sentiment_edge | narrative_pulse | null",
+            "nullable": true,
+            "type": "string"
+          },
+          "chains": {
+            "description": "Blockchain networks, e.g. ['bitcoin', 'ethereum']",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "createdAt": {
+            "description": "When this alert was generated",
+            "format": "date-time",
+            "type": "string"
+          },
+          "id": {
+            "description": "Unique alert identifier, e.g. 'ga-1719220800000-abc123'",
+            "type": "string"
+          },
+          "severity": {
+            "description": "'high' (confidence ≥70%) | 'medium' (45–69%) | 'low' (<45%)",
+            "type": "string"
+          },
+          "summary": {
+            "description": "Signal summary combining whale moves, volume, and Fear & Greed context",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable alert title, e.g. 'Fear Buy Opportunity'",
+            "type": "string"
+          },
+          "tokens": {
+            "description": "Token symbols involved, e.g. ['BTC', 'ETH']",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "type": {
+            "description": "Alert classification: accumulation | fear_buy | smart_money_loading | volume_breakout | whale_convergence",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "refreshedAt": {
+      "description": "When the cron job last populated the cache; null if cache is empty",
+      "format": "date-time",
+      "nullable": true,
+      "type": "string"
+    },
+    "total": {
+      "description": "Number of alerts in the snapshot",
+      "type": "number"
+    },
+    "updatedAt": {
+      "description": "Response generation timestamp",
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Richly discloses behavior beyond the readOnly/idempotent annotations: reads from cache with no AI query, omits pro-only fields, maps severity thresholds, and defines alert types. It also outlines the response shape and field meanings, all without contradicting the 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 dense but mostly efficient, packing cache behavior, alert types, severity mapping, and response schema into a compact block. Minor redundancy exists in repeating "snapshot" and "latest" early on, and the final sentence is truncated at "No authentic," which is a structural blemish.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is thorough for a zero-param read-only endpoint: refresh cadence, cache semantics, field omissions, alert taxonomy, and severity thresholds are all covered. The only gap is the unfinished sentence about authentication, which may leave an agent uncertain about access requirements.

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, so the description adds all necessary semantic context and the baseline of 4 applies. No parameter documentation is needed beyond what the empty schema states.

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 "Returns the latest snapshot of CryptoWhaleInsights Golden Alerts," giving a specific verb, resource, and scope. It further differentiates from siblings like golden_alerts_history and golden_alerts_monthly by emphasizing "latest," "refreshed every 5 minutes," and "up to 27 high-signal market alerts."

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 clearly establishes this tool is for the current snapshot by stating it reads from an in-process cache and refreshes every 5 minutes, implying use when current state is needed. It does not explicitly name alternative tools for historical data, but the "latest snapshot" framing gives sufficient situational context.

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

All whale-insights tools Inspect

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

Need Help?