Skip to main content
Glama
Sign In
whale-insights

whale-insights

by cryptowhaleinsights-ux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

burn_tracker

Track recent token burn events and 14-day burn history for ETH, SOL, and BNB. Get explorer-verifiable transactions and daily burn volume from Etherscan, Blockchair, and Solana RPC.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "burn_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden, and it discloses caching behavior ('Cached ~5min', 'no per-request AI cost'), subscription gating, and source aggregation across Etherscan, Blockchair, and Solana RPC. It doesn't specify output structure or rate limits, so 4 rather than 5.

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 opening line repeats itself: it first lists events/history/sources, then restates the same content with parenthetical detail, and the final two cache notes could be merged. Front-loaded but redundantly structured.

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?

For a zero-parameter cache-backed data tool, it covers purpose, sources, data freshness/caching, preview limits, and subscription requirement. Absence of an output schema is mitigated by the description naming the returned event/history concepts, though exact fields are still unspecified.

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 properties, so there are no parameters needing explanation; the 100% schema coverage baseline combined with 0 params supports a 4.

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?

States a specific action and resource: 'Get token burn events and 14-day burn history' for ETH, SOL, and BNB, naming data sources. This makes it clearly distinct from the other data/history siblings, even though no sibling is explicitly contrasted.

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?

Provides practical context for invoking it: free preview is limited to top 3 events, full list requires Weekly Alpha subscription, and responses are cached. It doesn't contrast with sibling tools or state exclusions, so it stops short of a 5.

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

Deploy Server

Other Tools