Whale transaction tracker -- large on-chain transfers with sender, value, USD estimate. Market-moving alerts.
Single tool 'crypto_track_whale_transactions' has a well-structured description (280+ chars) with clear use cases and anti-patterns documented. Input schema is present with two parameters (chain, minValue), both with descriptions. However, the schema lacks explicit type constraints (enums for chain, min/max bounds for minValue). Output schema is documented in the description but not formally in the tool definition. Parameter descriptions are adequate but could be more prescriptive about valid values and ranges. No error handling guidance provided.
Use this when you need to track large on-chain transactions (whale movements) on Ethereum or Base. Returns recent high-value transfers in JSON. 1. transactions: array of whale transfers sorted by value descending 2. from: sender wallet address 3. to: receiver wallet address 4. valueEth: transaction value in ETH 5. valueUsd: estimated USD value at time of transfer 6. txHash: transaction hash for on-chain verification 7. blockNumber: block number of the transaction 8. timestamp: when the transaction occurred Example output: {"transactions":[{"from":"0xab...","to":"0xcd...","valueEth":500.0,"valueUsd":1552500,"txHash":"0xef...","blockNumber":19845632,"timestamp":"2026-04-13T11:22:00Z"}],"chain":"ethereum","minValue":100,"totalFound":8} Use this FOR detecting market-moving whale activity and smart money flows. Essential for trading signal generation and on-chain intelligence. Do NOT use for wallet balance -- use wallet_get_portfolio instead. Do NOT use for token prices -- use finance_get_token_price instead. Do NOT use for holder distribution -- use token_get_holder_analysis instead.
Input schema lacks enum constraint for 'chain' parameter. Currently accepts free-form string; should declare enum: ['ethereum', 'base'] to prevent hallucinated chain names.
minValue parameter has no bounds declared. Schema should specify minimum: 0 and maximum (e.g., 10000) to prevent LLMs from passing absurd values that break the API.
Output schema documented only in description text, not in formal JSON Schema. LLMs cannot reliably parse prose descriptions of response structure. Define a formal outputSchema property.
No error handling guidance. Tool description lacks recovery hints (e.g., 'If no transactions found, try lowering minValue' or 'If API rate-limited, retry after 60s'). Agents have no guidance on failure modes.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2025-06-18+ | v2 |
Tool name 'crypto_track_whale_transactions' is 31 chars (above p90=27 baseline). Consider 'track_whale_transfers' (21 chars) for clarity and brevity. Current name is acceptable but verbose.