Skip to main content
Glama
predgeAI

whale-data-mcp

by predgeAI

Largest price movers

predge_markets_movers

Identify assets with the largest YES-price moves across active markets using trade prints. Filter results by 1h, 6h, or 24h windows.

Instructions

PAID (~$0.005). Largest YES-price moves across active markets (from trade prints). Param: window (1h|6h|24h, default 6h).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does reveal the cost (~$0.005) and data source (trade prints), which are useful behavioral traits. However, it omits rate limits, result size, pagination, or any side effects, leaving some uncertainty.

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?

The description is a single, tightly packed sentence: cost warning, core function, and parameter details are front-loaded. Every word contributes, and there is no redundancy or filler.

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?

The tool has one optional parameter and no output schema, so the description should clarify return shape, but it only states what the result is conceptually. It lacks details on the list format, number of entries, or sorting criteria. Adequate for a simple query but still incomplete.

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?

The schema has 0% description coverage, but the enum itself provides limited meaning. The description adds the default value (6h) and compacts the options, yet it doesn't explain how the window impacts the returned movers. This partially compensates for the schema gap but not fully.

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 explicitly states the tool returns largest YES-price moves across active markets from trade prints, which is a specific action and resource. It clearly differentiates from sibling tools focused on whales, signals, or history.

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?

The description does not provide any when-to-use guidance or compare against alternative tools like predge_market_history or predge_signals_market. The only hint is the paid nature, but no explicit scenarios or exclusions are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/predgeAI/whale-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server