Skip to main content
Glama

HPSILab Quant Finance

Implied Volatility Radar

get_iv_radar
Read-onlyIdempotent

Implied-volatility (IV) structure for a stock: how expensive options are, whether volatility is being squeezed, and whether traders are paying up for upside (calls) or downside (puts). Available to all signed-in users.

Returns spot price, the expiry used, the option quote time (latest trade
in the chain, UTC) and fetch time, ATM and 30-day IV, IV rank/percentile
with their basis, the 25-delta risk reversal in vol points, a squeeze
score and the volatility regime.

Args:
    ticker: Stock symbol, e.g. "NVDA".
    refresh: Bypass the backend's fresh IV cache and request the latest
        option-chain pull. Defaults to False.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_iv_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol, e.g. AAPL.
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"Stock ticker symbol, e.g. AAPL."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds meaningful context beyond that: it discloses the signed-in-user access requirement, the cache-bypass behavior, and the distinction between option quote time and fetch time. It does not mention rate limits or error behavior, keeping it from a 5.

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 front-loaded with the tool's purpose, followed by a useful Returns list (important because there is no output schema) and an Args section. It is appropriately sized and easy to scan. There is minor redundancy between the ticker example in the description and the schema's own example.

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?

For a two-parameter tool with no output schema, the definition covers what an agent needs: purpose, auth requirement, cache semantics, and a thorough list of return values including IV rank/percentile basis and freshness timestamps. It does not state what happens when a ticker has no options chain, which is a small remaining gap.

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?

Schema coverage is 50%: ticker is documented in the schema, but refresh has only a title and default. The description fully compensates by explaining that refresh bypasses the backend's fresh IV cache and requests the latest option-chain pull, with a stated default of False. The ticker example is repeated rather than extended, so it is not a perfect 5.

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

Purpose4/5

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

The description states a specific resource — implied-volatility structure for a stock — and enumerates the analytical questions it answers (option expensiveness, squeeze, upside/downside skew). This makes the tool's purpose clear without opening the schema. It does not explicitly differentiate itself from siblings such as get_option_pressure, so it stops short of a 5.

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?

Usage is implied by the enumerated questions the tool answers, and the note that it is 'Available to all signed-in users' gives access context. However, there is no explicit when-to-use guidance, no exclusions, and no reference to alternatives like get_option_pressure or get_pretrade_risk_scan.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.