Skip to main content
Glama

cortex_whale_alerts

Large-transfer / accumulation alerts with tx hashes + timestamps (Alchemy). Omit 'address' for a chain-wide scan. x402 paid: $0.050 USDC on Base per call.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain: ethereum, base, arbitrum, polygon, optimismethereum
limitNo
addressNoOptional wallet to watch
min_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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; it usefully discloses the paid x402 model ($0.050 USDC on Base per call) and the data provider, which an agent must know before invoking. It does not cover data freshness/latency, pagination behavior for the limit cap, or what happens if payment fails.

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 tight clauses — purpose + return fields, the key parameter rule, then billing — with the most decision-relevant information front-loaded. Nothing is wasted and no sentence merely restates the tool name.

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 4-parameter tool with no annotations and no output schema, the description does well to state the return fields and payment cost. But it leaves the threshold semantics (min_usd default $100k) and the limit cap behavior unexplained, and doesn't clarify which chains are supported despite the schema listing them.

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 50%, and the description compensates for exactly one gap: it explains the semantic effect of omitting 'address'. The remaining undocumented parameters (limit, min_usd) get no clarification beyond their defaults, so it adds partial value over 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?

Names a specific verb (alert on large transfers/accumulation), the resource (on-chain whale activity), the data source (Alchemy), and the payload (tx hashes + timestamps). An agent can tell this is a whale-alert feed, though it doesn't explicitly distinguish itself from the related sibling cortex_register_whale_webhook.

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?

Provides one concrete usage rule — 'Omit address for a chain-wide scan' — which tells the agent how to switch between scoped and global modes. However there is no guidance on when to prefer this over cortex_register_whale_webhook, cortex_tx_history, or cortex_wallet_intel, so sibling selection is left to inference.

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.