Basis Desk — crypto news & market data

Large on-chain transfers

whale_transfers

Read-onlyIdempotent

Large on-chain transfers ('whale moves') found by Basis Desk's own scanner: Ethereum ETH and major stablecoins/wrapped assets from $5M, Bitcoin from 100 BTC (change outputs excluded), with exchange wallet labels and direction (to/from exchange). Use for whale activity or exchange inflow/outflow questions. Last 7 days.

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

Input Schema

Name	Required	Description	Default
`chain`	No
`limit`	No
`min_usd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent, non-destructive profile, so the description is free to add domain behavior: the scanner's own inclusion thresholds ($5M ETH/stablecoins, 100 BTC), exclusion of Bitcoin change outputs, the 7-day window, and the fact that results carry exchange wallet labels plus direction. The one gap is that it never says what limits result count or whether the min_usd parameter can lower the built-in floor.

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 sentences, front-loaded with what the tool returns and immediately followed by usage and scope constraints. No filler; every clause carries information.

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?

There is no output schema and no per-parameter schema descriptions, so this description does a lot of compensating work: data source, thresholds, time window, and the shape of returned enrichment (labels, direction). It falls just short on the ambiguity between the described fixed thresholds and the tunable min_usd/limit parameters.

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 0%, so the description must carry the parameter burden. It does clarify which chains/assets are covered (Ethereum ETH, stablecoins, wrapped assets; Bitcoin) and hints at the dollar threshold semantics, but the relationship between the documented $5M/100 BTC thresholds and the min_usd parameter (which defaults to 10,000,000) is ambiguous, and 'limit' is never addressed.

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?

States a specific resource ('large on-chain transfers / whale moves'), the data source (Basis Desk's own scanner), and the exact thresholds that define inclusion, so the agent knows precisely what this returns. It is trivially distinguishable from the news/article siblings, which cover an entirely different domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use for whale activity or exchange inflow/outflow questions,' giving a clear use case trigger. It does not name a competing alternative tool, but none of the siblings (news, safety, market snapshot) overlap in purpose, so the routing guidance is sufficient.

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

All Basis Desk — crypto news & market data 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.

Resources

Need Help?