Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_snapshot_open_interest

Fetch the last open interest for an option contract, reported each day at 06:30 ET.

Instructions

[VALUE] Last open interest for an option contract. Reported ~06:30 ET daily.

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.
min_timeNoFilters snapshots to include only data with a timestamp greater or equal to the specified value (HH:mm:ss.SSS format).
expirationYesThe expiration of the contract in `YYYY-MM-DD` or `YYYYMMDD` format, or `*` for all expirations.
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.
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds a key non-obvious trait: the value is reported daily at ~06:30 ET, meaning data is a once-daily snapshot. It does not cover rate limits, error cases, or reversibility, but the daily report time is valuable context.

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 short sentences, front-loaded with the core purpose. No redundant or repetitive content. It is appropriately sized for the tool's simplicity.

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?

Given 7 parameters with full schema coverage and no output schema, the description provides adequate context: what it returns (last open interest) and the daily update time. It could be more explicit about the return format or the distinction from historical tools, but it is complete enough for basic selection.

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%, so baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides. It mentions 'for an option contract' but does not elaborate on filters like strike or right.

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 identifies the resource (open interest) and the context (last value for an option contract). It distinguishes from sibling snapshot tools (quote, trade, OHLC) by naming open interest specifically. However, it lacks an explicit verb like 'Get' or 'Retrieve', and the '[VALUE]' prefix is a bit ambiguous.

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 daily reporting time (~06:30 ET) implies this is the latest daily snapshot, but it does not explicitly guide on when to use this vs. option_history_open_interest or other snapshot tools. No alternatives or exclusions are mentioned.

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