Skip to main content
Glama
haiyunsky

HPSILab - Quant Finance MCP Server for Stock Analysis and Options Analytics

get_iv_radar

Assess whether options are cheap or expensive using IV rank and percentile. Determine volatility regime and risk-reversal direction for strategy selection.

Instructions

Retrieve implied-volatility (IV) metrics for a single stock.

Use this tool when:

  • You need to assess whether options are cheap or expensive relative to historical norms (IV rank / IV percentile).

  • You want the current volatility regime ("Low", "Normal", "Elevated", "Extreme") to frame risk sizing or strategy selection.

  • You are analyzing skew or risk-reversal direction (put-heavy vs call-heavy market).

Do NOT use this tool if you already called analyze_stock — the IV data is included in that response.

Parameters

symbol : str Exchange ticker in uppercase, e.g. "TSLA", "NVDA", "IWM".

Returns

dict with keys: symbol : str — normalized ticker atm_iv : float — at-the-money implied volatility (annualized %) iv_rank : float — 0–100; ≥80 = expensive, ≤20 = cheap iv_percentile : float — historical percentile (0–100) risk_reversal : float — 25-delta risk reversal (positive = call-skew) volatility_regime: str — "Low" | "Normal" | "Elevated" | "Extreme"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesExchange ticker in uppercase, e.g. 'TSLA', 'NVDA', 'IWM'. Do NOT pass company names — use official tickers only.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the return structure and key metrics, which partially addresses transparency. However, it does not disclose behavioral traits such as authorization requirements, rate limits, or error handling. The read-only nature is implied but not explicitly stated.

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 concise and well-structured: a one-line summary, bulleted use cases, a do-not-use note, and formatted parameters/returns. Every sentence adds value, and the key information is front-loaded.

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?

Given the tool's low complexity (single parameter, no output schema), the description is complete. It covers return fields, usage scenarios, and sibling differentiation. Minor omission: no mention of error behavior for invalid symbols, but overall sufficient.

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 input schema provides complete coverage (100%) with description, pattern, and examples for the single 'symbol' parameter. The tool description repeats this info but does not add new semantic meaning beyond the schema. Baseline 3 is appropriate.

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 'Retrieve implied-volatility (IV) metrics for a single stock' and lists specific metrics (IV rank, percentile, volatility regime, risk reversal). It also explicitly distinguishes from the sibling 'analyze_stock' by noting that the IV data is included in that response, thus differentiating the tool's purpose.

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

Usage Guidelines5/5

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

The description provides explicit 'Use this tool when:' scenarios (assessing options cheapness, current volatility regime, skew analysis) and a clear 'Do NOT use' condition (if already called analyze_stock). This gives concrete guidance on when to invoke this tool versus alternatives.

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/haiyunsky/hpsilab-quant-finance-mcp'

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