Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_history_open_interest

Fetch historical options open interest for a symbol and expiration. Filter by strike, right, and date to get prior day's reported values as of 06:30 ET.

Instructions

[VALUE] Historical open interest for options. Reported ~06:30 ET, reflects prior day.

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.
max_dteNoIf specified, only contracts with a full calendar day 'Days to Expiration' (DTE) less than or equal to this number will be returned.
end_dateNoThe end date (inclusive).
expirationYesThe expiration of the contract in `YYYY-MM-DD` or `YYYYMMDD` format, or `*` for all expirations.
start_dateNoThe start date (inclusive).
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.
Behavior3/5

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

The description discloses the data's reporting time and that it reflects the prior day, which is valuable context beyond the schema. However, it doesn't outline other behaviors like date range handling, default symbols, or response format.

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 very brief and front-loaded with the core purpose. However, the '[VALUE]' prefix is an unexplained placeholder that slightly detracts from clarity.

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?

With 9 parameters and no output schema, the description provides minimal guidance on how to construct requests or interpret responses. It lacks details on filtering behavior, date precedence, or output structure, making it incomplete for a tool of this complexity.

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 descriptions cover all 9 parameters at 100%, so the description doesn't need to add parameter details. The description adds no extra semantic meaning beyond the schema.

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 phrase 'Historical open interest for options' clearly identifies the tool as fetching historical open interest data, distinguishing it from snapshot and other history tools. The timing note adds context. The verb is implicit but unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It specifies that data is reported at ~06:30 ET and reflects prior day, setting expectations for data recency. However, it doesn't explicitly mention alternatives or when not to use this tool.

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