Skip to main content
Glama

get_whale_activity

Scans the given addresses and returns recent on-chain movements (large transfers, accumulation). Supports ETH, BTC and SOL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "watchlist": "<watchlist>"
    },
    "name": "get_whale_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchlistYesAddresses to watch (max. 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / watchlist / items / additionalProperties
      Removed value: -false
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose scope (address scanning), output content (large transfers, accumulation), and chain coverage (ETH/BTC/SOL). However, 'recent' is never defined as a lookback window, and there is no mention of rate limits, cost, or whether results are cached, which matters for a scan-style 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 compact sentences, front-loaded with the action and followed by the output and chain coverage. Nothing is padded or redundant beyond the brief chain enumeration.

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?

For a single-parameter scan tool with no output schema and no annotations, the description covers purpose and output shape adequately. It falls short on the temporal definition of 'recent', how 'accumulation' is detected, and any behavioral constraints, so it is viable but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the watchlist parameter and its maxItems are fully documented structurally. The description adds only marginal meaning by echoing the supported chains that already appear as the enum on the nested 'chain' field.

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?

States a concrete verb (scans) and resource (given addresses) and names what comes back: recent large transfers and accumulation signals. It is distinguishable from list_known_whales (which enumerates whales rather than scanning supplied addresses), though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

The description implies you must already have a set of addresses to monitor but gives no guidance on when to pick this over get_wallets, get_portfolio, or list_known_whales. There is no when-to-use / when-not-to-use statement or named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources