Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_history_quote

Get historical NBBO quotes for options. Supports interval aggregation, expiration filtering, and date ranges up to one month.

Instructions

[VALUE] NBBO quote history for options. Supports interval aggregation. Max 1 month, requires expiration.

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).
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
expirationYesThe expiration of the contract in `YYYY-MM-DD` or `YYYYMMDD` format, or `*` for all expirations.
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.
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 interval aggregation and a 1-month limit but does not describe the response format, whether bid/ask sizes are included, or error handling. This is insufficient for a data retrieval tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loads the core purpose, but the '[VALUE]' placeholder suggests a template error. While it contains no redundant sentences, it lacks the polished structure expected and feels underdeveloped.

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 the large schema (12 params), no annotations, and no output schema, this description is far too sparse. It doesn't explain the meaning of NBBO, the return format, or how this tool differs from other sibling quote/trade history tools, making it incomplete for effective selection and invocation.

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?

All 12 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds no parameter-specific information beyond what the schema already provides, such as date format details or filtering behavior, so it stays at baseline.

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 states 'NBBO quote history for options', which clearly identifies the tool's function as retrieving historical quote data. However, the leading '[VALUE]' placeholder is unprofessional and the description does not explicitly contrast with other option history tools, though the name and content do provide some differentiation.

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?

The description provides no guidance on when to use this tool over alternatives like option_history_trade_quote. It only mentions constraints ('Max 1 month, requires expiration'), which are limitations rather than usage scenarios or 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