Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_history_greeks_second_order

Fetch historical second-order option Greeks (Gamma, Vanna, etc.) from midpoint prices for a symbol and expiration, with date/time intervals and strike filters. Max one month per request.

Instructions

[PROFESSIONAL] Historical second-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.
Behavior3/5

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

Discloses the data source (midpoint prices) and a request limit (1 month). With no annotations provided, the description carries the burden, but it remains sparse, lacking details on pagination, return format, or rate limits. No contradiction with annotations since none exist.

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?

A single sentence with no fluff. Front-loads the core purpose and immediately provides a critical constraint. Very 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?

Given 15 parameters, no output schema, and complex interactions (e.g., interval restrictions for single-day requests), this description is too minimal. It omits important context about response structure, multi-day behavior, and how the 1-month limit should be handled. The schema helps but the description alone is insufficient for an agent to fully understand the tool.

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 the schema already documents all parameters. The description adds no additional parameter meaning beyond the existing schema descriptions.

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?

Clearly states it provides historical second-order greeks from midpoint prices. The phrase 'second-order' and 'midpoint prices' distinguishes it from sibling tools like first-order, third-order, and trade-based greeks history.

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?

Implies usage by name (second-order greeks history) and adds a key constraint (max 1 month per request). However, it does not explicitly state when to use this versus alternatives or provide exclusions.

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