Skip to main content
Glama
Sign In
whale-insights

whale-insights

by cryptowhaleinsights-ux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

live_stats

Check live activity counters for whale moves, active smart-money wallets, and golden alerts, refreshed every 10 seconds.

Instructions

Get live activity counters — whale moves today, smart-money wallets active, golden alerts (10s cache) — Live activity snapshot for the platform (real recent counts, no fabricated floors). Cached ~10s. Response includes meta.updatedAt and meta.cacheAgeSeconds (derived from the underlying whale-copy-signals cache timestamp; 0 when the cache is cold).

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": "live_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses caching behavior (~10s), data freshness ('no fabricated floors'), and response fields (meta.updatedAt, meta.cacheAgeSeconds). It does not mention any destructive behavior, which is consistent with a read-only tool.

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

Conciseness5/5

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

Two sentences, each earning its place: the first lists the core data and caching, the second details response fields. No wasted words, front-loaded with key purpose.

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?

Given no output schema, the description covers return structure (counters and meta) adequately. It could be slightly more detailed about the counter format, but it is complete enough for a simple snapshot tool.

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?

No parameters exist, so the baseline is 4. The description adds meaning by specifying the return content (live counters) and response meta fields, which is sufficient for a parameterless tool.

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 clearly states 'Get live activity counters' and enumerates specific metrics (whale moves today, smart-money wallets active, golden alerts), distinguishing it from siblings like 'recent_whales' which likely provides more detailed whale data.

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?

The description implies usage for a quick live snapshot but does not explicitly state when to use this tool versus siblings like 'status' or 'recent_whales'. No exclusions or alternatives are mentioned.

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