Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_history_greeks_third_order

Retrieve historical third-order option Greeks (speed, zomma, color) calculated from midpoint prices. Ideal for advanced risk analysis and backtesting over any period up to one month.

Instructions

[PROFESSIONAL] Historical third-order greeks from midpoint prices. Max 1 month per request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoThe date to fetch data for. If present, this overrides start_date and end_date.
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.
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
end_dateNoThe end date (inclusive).
end_timeNoThe end time (inclusive) in the specified day.16:00:00
intervalYesThe size of the time interval must be one of the available options listed below. Intervals less than 1m are available only for single-day requests.1s
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.
rate_valueNoThe interest rate, as a percent, to be used in a Greeks calculation.
start_dateNoThe start date (inclusive).
start_timeNoThe start time (inclusive) in the specified day.09:30:00
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 of behavioral disclosure. It mentions the data source (midpoint prices) and a request limit, but does not disclose whether this is a read-only operation, what the output format is, or any pagination/permission considerations. This leaves significant unknowns for the agent.

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 two sentences with no filler. It front-loads the primary purpose and includes a key constraint, making it highly efficient.

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?

Despite the rich schema, the tool has no output schema and no annotations. The description does not explain the return structure, the meaning of 'third-order greeks,' or how to handle multi-day requests. For a tool with 15 parameters and complex behavior, this is incomplete.

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 descriptions for all 15 parameters (100% coverage), so the description need not add parameter details. The description itself does not add any parameter-level meaning beyond the schema, making the baseline 3 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 the tool returns historical third-order greeks computed from midpoint prices. This distinguishes it from sibling tools like option_history_trade_greeks_third_order, which likely use trade prices. The verb 'Historical' and resource 'third-order greeks' are specific and unambiguous.

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?

The description includes a usage constraint (max 1 month per request) but does not explicitly state when to use this tool over alternatives such as the trade-based version. The context is implied by the midpoint price source and the historical nature, but exclusions are not provided.

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