whale-insights

leverage_picks_summary

Get Leverage Radar pick accuracy summary — historical win rate, avg return, and total pick counts across all recorded Best Trade Now picks — Aggregate accuracy statistics for all 'Best Trade Now' picks recorded by the Leverage Radar tool. Picks are saved automatically every 5 minutes when a high-confidence setup (score ≥ 60) is detected across 1h/4h/12h windows. Outcome is resolved after the close window elapses using live price data: win = +1.5% return for buy / −1.5% for sell. Records are permanent (never deleted) — this is a live data-provider proof-of-accuracy archive. Full pick list with entry/exit prices is Pro-only. 30-min cache.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: automatic saving, outcome resolution using live price data with specific win criteria, permanent record retention, and a 30-minute cache. This provides excellent transparency about how the tool operates.

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 dense with useful information and front-loaded with the main purpose. While it is somewhat long, every sentence contributes value. Minor redundancy could be trimmed, but overall well-structured.

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

Completeness5/5

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

Given no output schema and no annotations, the description covers behavior, data freshness, limitations, and accuracy metrics. It provides enough context for an agent to understand the tool's purpose and output without needing additional information.

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

Parameters4/5

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

There are zero parameters, and the schema coverage is 100% (empty). The description adds context about the data source and aggregation, which is sufficient. Baseline for zero parameters is 4.

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 that the tool gets a summary of Leverage Radar pick accuracy, including historical win rate, average return, and total pick counts. It specifies the data source (Best Trade Now picks) and distinguishes from related tools like leverage_history and leverage_radar by focusing on accuracy summary.

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 explains the context of when picks are saved (every 5 minutes on high-confidence setups) and limitations (full list is Pro-only), but it does not explicitly guide when to use this tool versus alternatives among the many sibling tools. Usage context is implied but not directly stated.

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

All whale-insights tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools have distinct purposes, but there are a few pairs with overlapping boundaries (e.g., analysts_signals vs analysts_signals_all, whale_movements vs whale_movements_summary) that could cause minor confusion.

Naming Consistency4/5

Naming is predominantly snake_case and descriptive, with minor inconsistencies in plural/singular forms (e.g., 'analysts' vs 'analyst_archive'). Overall pattern is stable.

Tool Count2/5

With 55 tools, the server is quite heavy. While the scope is broad, many tools are history/monthly variants that could be combined, making the count feel inflated beyond what is ideal for a single server.

Completeness4/5

The tool set covers a wide range of crypto analytics domains (analysts, arbitrage, funding, whales, sentiment, etc.). Minor gaps exist (e.g., no direct token price endpoint), but overall it's a comprehensive surface.

Resources

Need Help?