whale-insights

burn_tracker

Read-onlyIdempotent

Get token burn events and 14-day burn history — ETH, SOL, BNB burns from Etherscan + Blockchair + Solana RPC (top 3 free) — Recent on-chain token burn events (with explorer-verifiable tx) plus a 14-day daily burn-volume history, sourced from Etherscan, Blockchair, and Solana RPC. Free preview: top 3 events; the full list requires a Weekly Alpha subscription. Served from cache (no per-request AI cost). Cached ~5min.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No
`events`	No
`history`	No
`updatedAt`	No
`dataSource`	No
`attribution`	No
`requiredTierForFull`	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"
+    },
+    "dataSource": {
+      "type": "string"
+    },
+    "events": {
+      "items": {
+        "properties": {
+          "burnAmountUsd": {
+            "type": "number"
+          },
+          "burnPercentage": {
+            "type": "number"
+          },
+          "burnedAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "chain": {
+            "type": "string"
+          },
+          "explorerUrl": {
+            "format": "uri",
+            "type": "string"
+          },
+          "tokenSymbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "history": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "eventCount": {
+            "type": "number"
+          },
+          "totalBurnUsd": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "requiredTierForFull": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Even with annotations marking the tool read-only and idempotent, the description adds valuable non-obvious behavior: only the top 3 events are available for free, the full list requires a Weekly Alpha subscription, responses are served from cache with no per-request AI cost, and the cache is refreshed every ~5 minutes. This goes well beyond what the annotations convey.

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 front-loaded with the core action and then introduces important caveats, which is effective. It loses some points for redundancy: the sources are listed twice ('from Etherscan + Blockchair + Solana RPC' and 'sourced from Etherscan, Blockchair, and Solana RPC'), and 'burn events' is repeated in both main clauses.

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 zero-parameter, read-only tool with an output schema and strong annotations, the description is complete. It specifies sources, the historical window, explorer-verifiable transactions, subscription limits, and cache behavior — an agent has everything needed 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 input schema has zero parameters, so the baseline of 4 applies. There are no parameter details to elaborate, though the description does clarify what a no-input call returns: recent burn events, a 14-day history, and the free/full preview boundary.

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 token burn events and 14-day burn history' — and clearly enumerates the assets (ETH, SOL, BNB), data sources, and the two output components (recent events and daily burn-volume history). This makes it easy for an agent to distinguish from the many analyst, whale, and market sibling tools.

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 intended use is clear: call this when token burn events or 14-day burn history is needed. It does not explicitly name alternatives or state when not to use it, but no sibling tool appears to cover burns, so the description provides enough context for correct selection.

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?