Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_history_trade

Fetch up to one month of tick-level option trade history. Requires an expiration date; optional filters for date, strike, and right.

Instructions

[STANDARD] Tick-level trade history for options. 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
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.
Behavior3/5

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

With no annotations, the description carries full burden. It discloses 'tick-level', 'Max 1 month', and 'requires expiration' which are useful behavioral traits, but omits other aspects like return format, pagination, or error behavior.

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 a single, front-loaded sentence that delivers essential information efficiently. No filler or redundancy, every word contributes value.

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?

For a tool with 11 parameters, no output schema, and no annotations, the description is incomplete. It lacks return value explanation, usage context relative to siblings, and any guidance on parameter interactions or output behavior.

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 the baseline is 3. The description only adds 'requires expiration', reinforcing the schema's required field without offering additional meaning beyond what's already in the input schema.

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 states 'Tick-level trade history for options' which identifies the tool's verb and resource. It distinguishes from quote or greeks siblings by specifying 'trade', though it doesn't mention alternatives like option_history_trade_quote.

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?

Provides constraints (max 1 month, requires expiration) but no explicit guidance on when to use this tool versus alternatives. Sibling tools such as option_history_eod or option_history_trade_quote are not referenced.

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