Skip to main content
Glama

Whale alert

whale_alert
Read-only

Scan a wallet's recent transaction history for large movements. Returns whale-sized transfers and token movements. Costs $0.01 USDC per call.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "whale_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
minSolAmountNoMinimum SOL amount to qualify as whale activity (default: 100)
walletAddressYesSolana wallet address to monitor (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuinely useful behavioral fact not in the annotations — the $0.01 USDC per-call cost — plus a rough statement of what comes back. It stops short of saying how far back 'recent' reaches or any rate limits.

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?

Three short sentences that are front-loaded with the action, then the return shape, then the cost. No filler or redundancy; each sentence contributes something an agent needs.

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 two-parameter read-only tool with full schema coverage and no output schema, the description gives enough to call it correctly and roughly know what comes back. Minor gaps remain around the lookback window and whether non-SOL token movements have their own thresholds.

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 coverage is 100% with both parameters documented, including minSolAmount's default of 100, so the schema carries the load. The description adds only the notion of 'whale-sized' thresholds and no extra syntax or edge-case guidance beyond the schema.

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 specific verb and resource: scan a wallet's recent transaction history for large movements, and clarifies output is whale-sized transfers and token movements. An agent can distinguish it from wallet_pnl or wallet_profile, though it never explicitly contrasts with the neighbouring volume_alert.

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 the use case (detect large transfers for a given wallet) and the $0.01 cost hints that calls should be deliberate, but it names no alternatives and gives no when-not-to-use conditions versus sibling wallet/transaction tools.

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