whale-insights

Get currently trending crypto tokens — top gainers by 24h volume from DexScreener + CoinGecko merged (5-min cache) — Currently trending tokens sourced from DexScreener + CoinGecko top-50, merged and ranked by 24h volume. 5-min cache; check meta.cacheAgeSeconds for exact age. meta.tokenCount reflects the number of tokens in the current response.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Response freshness metadata. 5-min cache; check `meta.cacheAgeSeconds` for exact age.
`tokens`	No
`updatedAt`	No
`attribution`	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"
+    },
+    "meta": {
+      "description": "Response freshness metadata. 5-min cache; check `meta.cacheAgeSeconds` for exact age.",
+      "properties": {
+        "cacheAgeSeconds": {
+          "description": "Seconds since the cache was last refreshed.",
+          "type": "integer"
+        },
+        "tokenCount": {
+          "description": "Number of tokens in this response.",
+          "type": "integer"
+        },
+        "updatedAt": {
+          "description": "ISO timestamp when this cache entry was populated.",
+          "format": "date-time",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "tokens": {
+      "items": {
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "priceChange24h": {
+            "type": "number"
+          },
+          "priceUsd": {
+            "type": "number"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "volume24h": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful context beyond annotations: the 5-minute cache, the ability to check `meta.cacheAgeSeconds` for exact age, and `meta.tokenCount` semantics, plus the source-merging logic.

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

Conciseness3/5

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

The description is somewhat redundant: the opening dash-clause and the following sentence both describe the same trending-token sourcing and ranking logic. It is still readable and front-loaded, but the repetition could be trimmed without losing information.

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 read-only, zero-parameter tool with a rich output schema and comprehensive annotations, the description is complete. It explains the data sources, ranking criteria, cache behavior, and how to interpret two key metadata fields — everything an agent needs to invoke it correctly.

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 there is nothing for the description to clarify about inputs. The baseline for no-parameter tools is 4, and the description appropriately focuses on explaining the result and metadata rather than parameter behavior.

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 verb and resource — 'Get currently trending crypto tokens' — and adds the precise ranking method (top gainers by 24h volume from DexScreener + CoinGecko merged). This clearly distinguishes the tool from the broad set of siblings by defining exactly what it returns.

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 phrase 'Get currently trending crypto tokens' provides clear context for when to use this tool. It does not explicitly name alternatives or state when not to use it, but the unique scope (trending by 24h volume, merged sources) makes the usage context evident.

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?