Skip to main content
Glama

FlashAlpha (Unofficial)

Flashalpha Iv

flashalpha_iv
Read-onlyIdempotent

Get an implied-volatility summary for a stock, IV rank and IV percentile (plus current/underlying IV where available). Use to gauge whether options are relatively cheap or expensive. Example: flashalpha_iv({ symbol: "AAPL", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "AAPL",
      "_apiKey": "your-flashalpha-api-key"
    },
    "name": "flashalpha_iv"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol, e.g. "AAPL", "TSLA"
_apiKeyYesFlashAlpha API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered by structured fields. The description adds one useful behavioral hint — that current/underlying IV is only present 'where available' — but says nothing about rate limits, data freshness, or failure behavior when a symbol has no options.

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?

Purpose and the key returned metrics come first, followed by a short usage note. The trailing example call largely duplicates the schema's examples block, making it the one sentence that does not fully earn its place.

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?

With no output schema, the description carries the burden of saying what comes back, and it does list IV rank, IV percentile, and current/underlying IV. For a two-parameter read-only metric tool this is nearly sufficient; only data-freshness and null-handling caveats are missing.

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?

Schema description coverage is 100%, so both parameters (symbol, _apiKey) are already documented, including ticker examples. The description's inline example adds marginal clarity on invocation shape but no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource: 'Get an implied-volatility summary for a stock, IV rank and IV percentile'. This clearly separates it from greeks/GEX-style siblings by naming the IV metrics returned. It does not explicitly name a sibling it is not, 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?

Provides a use case ('Use to gauge whether options are relatively cheap or expensive'), which implies when the tool is appropriate. It gives no when-not conditions and no explicit routing to alternatives such as flashalpha_greeks, leaving the agent to infer boundaries.

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.