Skip to main content
Glama
Open-Agent-Tools

Open Stocks MCP

by Open-Agent-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

option_historicals

Retrieve historical price data for a stock option contract by specifying symbol, expiration date, strike price, and option type.

Instructions

Gets historical price data for an option contract.

Args:
    symbol: Stock ticker symbol (e.g., "AAPL")
    expiration_date: Expiration date in YYYY-MM-DD format
    strike_price: Strike price as string
    option_type: Option type ("call" or "put")
    interval: Time interval (default: "hour")
    span: Time span (default: "week")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
expiration_dateYes
strike_priceYes
option_typeYes
intervalNohour
spanNoweek

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as idempotency, rate limits, or error handling. It merely lists parameters, leaving the agent to infer behavior from the tool name.

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 concise and front-loaded with the purpose. It uses a clear docstring format with listed parameters. No extraneous information, but could be more structured (e.g., consistent phrasing).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists, the description adequately covers input parameters and purpose. However, it lacks details on pagination, data frequency, or any caveats. The presence of sibling tools suggests more context could help distinguish usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description only restates parameter names (e.g., 'Stock ticker symbol' for symbol). While it provides default values for interval and span, it adds minimal semantic value beyond what the schema already indicates.

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?

Description clearly states it retrieves historical price data for an option contract, specifying the resource and action. It is distinct from sibling tools like price_history (stock) and options_chains (listing).

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 on when to use this tool versus alternatives like option_market_data or price_history. The description only states what it does without providing context on 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/Open-Agent-Tools/open-stocks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server