Gemral Edge

On-chain DEX Whale Swaps

get_onchain_whale_flows

On-chain decentralized exchange (DEX) large-scale swaps and liquidity pool transactions across tracked smart money wallets and verified token pools. Read-only evidence.

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

Input Schema

Name	Required	Description
`chain`	No	Blockchain network, e.g. solana, ethereum, arbitrum, base
`min_usd`	No	Minimum swap volume in USD
`token_symbol`	No	Token symbol, e.g. SOL, ETH
`window_hours`	No	Time window in hours

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

C2.5/5.0

Behavior1/5

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

The description states 'Read-only evidence,' but the annotations declare readOnlyHint=false. This is a direct contradiction about whether the tool is side-effect-free, and the description does not disclose any permissions, mutation behavior, or rate-limit context.

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 short and front-loads the resource scope. However, the final sentence is misleading given the annotations, so it does not fully earn its place despite the overall brevity.

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?

An output schema exists, so return values need not be explained. Still, the description leaves usage context absent and creates a serious behavioral ambiguity by calling the tool read-only while annotations say readOnlyHint=false.

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 all four parameters are already documented in the input schema. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as on-chain DEX large-scale swaps and liquidity pool transactions, but it is a noun phrase rather than a specific verb+resource statement. It does not distinguish this tool from nearby siblings such as scan_crypto_patterns or get_crypto_funding_extremes.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The phrase 'Read-only evidence' implies an investigative context but does not route the agent among competing tools.

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

All Gemral Edge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.