Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

option_snapshot_ohlc

Fetch real-time current-day OHLC for an option contract. Specify underlying symbol, expiration, strike, and call/put right to retrieve today's open, high, low, and close.

Instructions

[VALUE] Real-time current-day OHLC for an option contract.

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.
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. It only states 'Real-time current-day OHLC' but does not disclose any behavioral traits such as default strike_range, behavior when no filters are applied, or limitations like data freshness or rate limits.

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 a single sentence, highly concise and front-loaded. However, it begins with '[VALUE]' which appears to be a placeholder and adds no semantic value, slightly reducing 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?

Despite having 7 parameters and no output schema or annotations, the description is extremely minimal. It fails to explain the response structure, how parameters like strike_range or min_time affect results, or any edge cases. This is insufficient for an agent to use the tool effectively.

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?

The input schema has 100% coverage for all 7 parameters, each with detailed descriptions. The tool description adds no extra parameter semantics, but the schema already provides sufficient meaning, so the baseline of 3 applies.

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 description clearly states the tool provides real-time current-day OHLC data for an option contract, using a specific verb+resource+scope. This distinguishes it from sibling tools like option_snapshot_trade (which provides trades) and option_history_ohlc (which provides historical OHLC).

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of scenarios where other option_snapshot_* tools would be more appropriate, nor any exclusions or prerequisites.

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