whale-insights

market_heatmap

Read-onlyIdempotent

Get token market heatmap — top tokens ranked by 24h performance with volume, market cap, chain (5-min cache) — Market-wide token heatmap: top tokens by 24h volume with price change, volume, market cap, and chain, blended from CoinGecko top markets plus emerging/hidden-gem tokens. Non-gated. Cached ~5min.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No
`chains`	No
`tokens`	No
`attribution`	No
`lastUpdated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "chains": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "lastUpdated": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "tokens": {
+      "items": {
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "marketCap": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "priceChange24h": {
+            "type": "number"
+          },
+          "priceUsd": {
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "volume24h": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description adds meaningful behavioral context: results are cached for ~5 minutes, access is non-gated, and data is blended from CoinGecko top markets plus emerging/hidden-gem tokens. This helps an agent set expectations about freshness and coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description repeats itself: the opening phrase and the following clause both say the same thing about a market-wide heatmap with tokens, volume, market cap, and chain. It also creates ambiguity by saying 'ranked by 24h performance' first and then 'top tokens by 24h volume,' which are not clearly the same ranking.

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

Completeness3/5

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

With no required parameters and an output schema present, the description covers most of what an agent needs: data fields, geo/access status, cache cadence, and source. However, the conflicting ranking phrasing ('24h performance' vs '24h volume') leaves the agent uncertain about how results are ordered.

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 parameter semantics are inherently non-issue. The description enriches the call by describing what the heatmap contains without needing to explain any inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb and resource ('Get token market heatmap') and clearly states the returned data: top tokens, 24h performance, volume, market cap, chain. It distinguishes itself from sibling tools reasonably well, though it does not explicitly contrast with overlapping tools like market_context or trending.

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

Usage Guidelines3/5

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

Provides useful context such as 'Market-wide token heatmap' and 'Non-gated', implying this is a general-purpose broad market snapshot with no authentication requirement. However, it never explicitly states when to use this tool instead of alternatives or when it should not be used.

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?