Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_snapshot_greeks_all

Retrieve real-time option Greeks for all contracts on a given expiration. Provide a symbol and expiration date to get current values for every strike and option type.

Instructions

[PROFESSIONAL] Real-time greeks for all contracts on an expiration. Use expiration=* for all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rightNoThe right (call or put) of the contract.both
strikeNoThe strike price of the contract in dollars (ie `100.00` for `$100.00`), or `*` for all strikes.*
symbolYesThe stock or index symbol, or underlying symbol for options.
max_dteNoIf specified, only contracts with a full calendar day 'Days to Expiration' (DTE) less than or equal to this number will be returned.
versionNoUsed to adjust Greeks calculation methodology. "1" uses a fixed .15 DTE for 0DTE; "latest" uses real TTE (down to a minimum of 1 hour)latest
min_timeNoFilters snapshots to include only data with a timestamp greater or equal to the specified value (HH:mm:ss.SSS format).
rate_typeNoThe interest rate type to be used in a Greeks calculation.sofr
expirationYesThe expiration of the contract in `YYYY-MM-DD` or `YYYYMMDD` format, or `*` for all expirations.
rate_valueNoThe interest rate, as a percent, to be used in a Greeks calculation.
stock_priceNoThe underlying stock price to be used in the Greeks calculation.
strike_rangeNoUsed to specify a filter to limit the number of contracts returned relative to the underlying's spot price. Will return the specified number of strikes above and below the spot price, as well as the at-the-money strike.
annual_dividendNoThe annualized expected dividend amount to be used in Greeks calculations.
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only mentions 'Real-time' and the wildcard expiration hint, but fails to disclose output structure, defaults, rate limits, or how the many parameters interact.

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 extremely concise, containing one purpose sentence and a practical hint. The '[PROFESSIONAL]' prefix adds minimal value but does not significantly detract.

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?

For a tool with 12 parameters and no output schema, this description is inadequate. It does not clarify which Greeks are returned, the response format, or how it differs from other greeks snapshot tools.

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 detailed parameter descriptions (e.g., right, strike, expiration, version). The description adds no extra semantics beyond the schema, so the baseline of 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?

The description clearly states the tool provides real-time greeks for all contracts on an expiration, which indicates a bulk snapshot operation. It distinguishes from sibling tools by emphasizing the 'all contracts' scope, though it does not explicitly contrast with first/second/third order greeks tools.

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?

No guidance is given on when to use this tool vs. alternatives like option_snapshot_greeks_first_order or option_history_greeks_all. The only usage hint is 'Use expiration=* for all,' which is a parameter tip rather than tool selection guidance.

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/drmartell/thetadata-mcp'

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