Skip to main content
Glama
erikmaday

unusual-whales-mcp

by erikmaday

uw_stock

Read-onlyIdempotent

Access Unusual Whales stock data: options chains, greeks, IV, OHLC candles, open interest, and more to analyze market sentiment and risk.

Instructions

Access UnusualWhales stock data including options chains, greeks, IV, OHLC candles, open interest, and more.

Available actions:

  • info: Get stock information (ticker required)

  • ohlc: Get OHLC candles (ticker, candle_size required; date, timeframe, end_date, limit optional)

  • option_chains: Get option chains (ticker required; date optional)

  • option_contracts: Get option contracts (ticker, expiry required; option_type, filters, limit optional)

  • greeks: Get greeks data (ticker, expiry required; date optional)

  • greek_exposure: Get gamma/delta/vanna exposure (ticker required; date, timeframe optional)

  • greek_exposure_by_expiry: Get greek exposure by expiry (ticker required; date optional)

  • greek_exposure_by_strike: Get greek exposure by strike (ticker required; date optional)

  • greek_exposure_by_strike_expiry: Get greek exposure by strike and expiry (ticker, expiry required; date optional)

  • greek_flow: Get greek flow (ticker required; date optional)

  • greek_flow_by_expiry: Get greek flow by expiry (ticker, expiry required; date optional)

  • iv_rank: Get IV rank (ticker required; date, timespan optional)

  • interpolated_iv: Get interpolated IV (ticker required; date optional)

  • max_pain: Get max pain (ticker required; date optional)

  • oi_change: Get OI change (ticker required; date, limit, page, order optional)

  • oi_per_expiry: Get OI per expiry (ticker required; date optional)

  • oi_per_strike: Get OI per strike (ticker required; date optional)

  • options_volume: Get options volume (ticker required; limit optional)

  • volume_oi_expiry: Get volume/OI by expiry (ticker required; date optional)

  • atm_chains: Get ATM chains for given expirations (ticker, expirations required)

  • expiry_breakdown: Get expiry breakdown (ticker required; date optional)

  • flow_per_expiry: Get flow per expiry (ticker required)

  • flow_per_strike: Get flow per strike (ticker required; date optional)

  • flow_per_strike_intraday: Get intraday flow per strike (ticker required; date, filter optional)

  • flow_recent: Get recent flow (ticker required; side, min_premium optional)

  • net_prem_ticks: Get net premium ticks (ticker required; date optional)

  • nope: Get NOPE data (ticker required; date optional)

  • stock_price_levels: Get stock price levels (ticker required; date optional)

  • stock_volume_price_levels: Get volume price levels (ticker required; date optional)

  • spot_exposures: Get spot exposures (ticker required; date optional)

  • spot_exposures_by_expiry_strike: Get spot exposures by expiry/strike (ticker, expirations required; date, filters optional)

  • spot_exposures_by_strike: Get spot exposures by strike (ticker required; date, filters optional)

  • spot_exposures_expiry_strike: Get spot exposures for specific expiry (ticker, expirations required; date, strike filters optional)

  • historical_risk_reversal_skew: Get risk reversal skew (ticker, expiry, delta required; date, timeframe optional)

  • volatility_realized: Get realized volatility (ticker required; date, timeframe optional)

  • volatility_stats: Get volatility stats (ticker required; date optional)

  • volatility_term_structure: Get term structure (ticker required; date optional)

  • stock_state: Get stock state (ticker required)

  • insider_buy_sells: Get insider buy/sells for stock (ticker required; limit optional)

  • ownership: Get ownership data (ticker required; limit optional)

  • tickers_by_sector: Get tickers in sector (sector required)

  • ticker_exchanges: Get mapping of all tickers to their exchanges (no params required)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

The description implies parameters (ticker, expiry, etc.) but the input schema declares no properties, creating a direct contradiction. Annotations indicate read-only and idempotent behavior, but the description fails to address this mismatch or other behavioral traits like rate limits.

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

Conciseness3/5

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

The description is front-loaded with the purpose but becomes verbose with a long list of 30+ actions. Each line is informative, but the overall length could overwhelm an agent. Structure is clear but not concise.

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 covering many actions, the description omits the parameter structure (missing from schema), return format, usage examples, and authentication needs. For a complex tool with no output schema, this is insufficient.

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?

With zero parameters in the schema, baseline is 4 according to rules. The description adds rich parameter info for each action (e.g., ticker required, optional filters), but these are not formalized in the schema, reducing reliability. Overall, it adds value but is inconsistent.

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 states the tool accesses UnusualWhales stock data, but the input schema has no properties, contradicting the detailed parameter requirements listed for each action. This inconsistency undermines clarity, making it unclear what the agent should send.

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 lists many actions but provides no guidance on when to use this tool versus sibling tools like uw_options or uw_flow. No context on use cases or exclusions is 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/erikmaday/unusual-whales-mcp'

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