x402-dex-intel

Overview Schema Source Related Servers Discussions Admin

get_whale_flow

Track 1-hour smart money accumulation, net whale inflow in USD, and cluster accumulation confidence signals for any token on Base.

Instructions

Tier 3 ($0.10 USDC): Fetches 1h smart money accumulation, net whale inflow (USD),
and cluster accumulation confidence signals.

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": {
      "token": "<token>"
    },
    "name": "get_whale_flow"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions that the tool fetches data (implying read-only) and includes cost information, but it does not disclose authentication needs, rate limits, or potential side effects. Given the lack of annotations, this is insufficient.

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

Conciseness4/5

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

The description is a single concise sentence, front-loaded with cost and then the action. It avoids redundancy and is easy to parse, though it could have included more detail on the parameter without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only one parameter and an output schema, the lack of return value explanation is acceptable. However, the absence of usage guidance and parameter semantics makes the description incomplete for a simple tool, limiting its overall usefulness.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the parameter. However, it does not elaborate on what 'token' means (e.g., address, symbol, format). The only clue is the name, which is not sufficient for unambiguous use.

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 the verb 'Fetches' and the specific resource: 1h smart money accumulation, net whale inflow (USD), and cluster accumulation confidence signals. It differentiates from sibling tools which focus on orderbook depth and market pulse, making its distinct purpose evident.

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 provides no explicit guidance on when to use this tool versus alternatives. The usage is implied by the tool's name and description—for whale flow analysis—but there are no explicit conditions, exclusions, or mentions of preferable scenarios.

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

Deploy Server