mcp-livedatapro

getOptionsChainGreeks

Real-time equity and index options chains, strike prices, implied volatility (IV), delta, gamma, theta, and open interest. Use when fetching equity or index options contracts (calls and puts), strike prices, bid/ask spreads, Implied Volatility (IV), Open Interest, and Black-Scholes Greeks (Delta, Gamma, Theta) for a specific expiration date. Do not use for spot stock closing prices (use getStockEodPrices).

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>",
      "expiration_date": "<expiration_date>"
    },
    "name": "getOptionsChainGreeks"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Uppercase underlying equity or ETF ticker symbol (e.g., SPY, QQQ, AAPL, NVDA).
`expiration_date`	Yes	Option contract expiration date in ISO YYYY-MM-DD format.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / expiration_date / examples
```
Added value: +[
+  "2026-12-18"
+]
```
- addedInput schema / properties / expiration_date / format
```
Added value: +"date"
```
- addedInput schema / properties / expiration_date / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
- addedInput schema / properties / ticker / examples
```
Added value: +[
+  "SPY"
+]
```
- addedInput schema / properties / ticker / pattern
```
Added value: +"^[A-Z]{1,6}$"
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / expiration_date / description

Previous value: -"Option expiry date (YYYY-MM-DD)"New value: +"Option contract expiration date in ISO YYYY-MM-DD format."

changedInput schema / properties / ticker / description

Previous value: -"Underlying asset ticker (e.g., SPY, AAPL, QQQ)"New value: +"Uppercase underlying equity or ETF ticker symbol (e.g., SPY, QQQ, AAPL, NVDA)."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key trait 'Real-time' data and scopes the query to a single expiration date, but says nothing about chain size, pagination, rate limits, or what an invalid/missing expiration yields.

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?

Two sentences, front-loaded with the resource and followed by routing guidance. Slight redundancy: IV, open interest, and the Greeks are enumerated twice (once in the opening list, once in the 'Use when' clause), costing some economy.

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 annotations and no output schema, the description compensates by listing the returned fields (strike, bid/ask, IV, open interest, Delta/Gamma/Theta), giving the agent a usable picture of the response. Edge-case behavior (no chain for that expiration, empty results) is not covered.

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 coverage is 100% with only two required parameters, and the schema itself documents the uppercase ticker pattern and ISO date format. The description mentions 'a specific expiration date' and 'underlying equity or index,' which corroborates but does not extend the schema detail. Baseline 3 applies.

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?

Names the specific resource (equity/index options chains) and enumerates the exact data returned: strikes, bid/ask, IV, open interest, and Black-Scholes Greeks for a given expiration. This is clearly distinguishable from the sibling getStockEodPrices, which is named explicitly.

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?

Provides an explicit 'Use when fetching equity or index options contracts... for a specific expiration date' clause and an explicit exclusion with a redirect: 'Do not use for spot stock closing prices (use getStockEodPrices).' Both the positive and negative routing conditions are stated.

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

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?