Skip to main content
Glama
erikmaday

unusual-whales-mcp

by erikmaday
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

uw_market

Read-onlyIdempotent

Get market-wide data including tide, sector ETFs, economic and FDA calendars, and more for informed trading decisions.

Instructions

Access UnusualWhales market-wide data including market tide, sector ETFs, economic calendar, FDA calendar, and more.

Available actions:

  • market_tide: Get market tide data showing net premium flow (date optional; otm_only, interval_5m optional)

  • sector_tide: Get sector-specific tide (sector required; date optional)

  • etf_tide: Get ETF-based tide (ticker required; date optional)

  • sector_etfs: Get SPDR sector ETF statistics

  • economic_calendar: Get economic calendar events

  • fda_calendar: Get FDA calendar (announced_date_min/max, target_date_min/max, drug, ticker, limit optional)

  • correlations: Get correlations between tickers (tickers required; interval, start_date, end_date optional)

  • insider_buy_sells: Get total insider buy/sell statistics (limit optional)

  • oi_change: Get top OI changes (date, limit, order optional)

  • spike: Get SPIKE values (date optional)

  • top_net_impact: Get top tickers by net premium (date, issue_types, limit optional)

  • total_options_volume: Get total market options volume (limit optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

D1.9/5.0
Behavior2/5

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

Annotations (readOnlyHint, idempotentHint) are consistent with read operations, but the description inadequately addresses the mismatch between the listed actions (with parameters) and the empty input schema, creating confusion about actual behavior.

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

Conciseness2/5

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

The description is structured with bullet points but is lengthy and contains redundant detail. The content is not concise given the inaccurate relationship to the schema.

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?

Despite listing many actions, the description lacks details on how to invoke them (no selector parameter), does not mention return values, and fails to explain the discrepancy with the input schema. Incomplete for a complex multi-action tool.

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

Parameters1/5

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

The input schema has no parameters (100% coverage), yet the description details actions with required/optional parameters. This adds misleading information that contradicts the schema, providing no helpful meaning.

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

Purpose2/5

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

The description lists many market-wide data actions (e.g., market_tide, sector_etfs) but the input schema is empty, providing no way to select an action. This makes the tool's purpose unclear and potentially misleading.

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?

No guidance on when to use this tool versus sibling uw_* tools. The description implies many capabilities but does not differentiate or advise on selection criteria.

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/erikmaday/unusual-whales-mcp'

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