Skip to main content
Glama
bartest5

Alpaca MCP Server

by bartest5
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_option_chain

Retrieve option chain data for a symbol, including quotes, implied volatility, and greeks. Filter by type, strike, expiration, and more to narrow results.

Instructions

Retrieves option chain data for an underlying symbol, including latest trade, quote, implied volatility, and greeks for each contract. The response can be very large. Use the type (call/put), strike_price_gte/lte, expiration_date, and limit parameters to narrow results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedNoThe source feed of the data. `opra` is the official OPRA feed, `indicative` is a free indicative feed where trades are delayed and quotes are modified. Default: `opra` if the user has a subscription, otherwise `indicative`. opra
typeNoFilter contracts by the type (call or put).
limitNoNumber of maximum snapshots to return in a response. The limit applies to the total number of data points, not the number per symbol! Use `next_page_token` to fetch the next set of responses.
page_tokenNoThe pagination token from which to continue. The value to pass here is returned in specific requests when more data is available, usually because of a response result limit.
root_symbolNoFilter contracts by the root symbol.
updated_sinceNoFilter to snapshots that were updated since this timestamp, meaning that the timestamp of the trade or the quote is greater than or equal to this value. Format: RFC-3339 or YYYY-MM-DD. If missing, all values are returned.
expiration_dateNoFilter contracts by the exact expiration date (format: YYYY-MM-DD).
strike_price_gteNoFilter contracts with strike price greater than or equal to the specified value.
strike_price_lteNoFilter contracts with strike price less than or equal to the specified value.
underlying_symbolYesThe financial instrument on which an option contract is based or derived.
expiration_date_gteNoFilter contracts with expiration date greater than or equal to the specified date.
expiration_date_lteNoFilter contracts with expiration date less than or equal to the specified date.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It adds a key behavioral trait: 'The response can be very large,' which warns about payload size. However, it doesn't disclose pagination behavior or data source (e.g., real-time vs delayed), which could affect invocation.

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?

Two sentences with no fluff. First sentence states the purpose, the second provides usage guidance. Immediately front-loaded with the action.

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 12 parameters and a rich output schema, the description covers the essential purpose and filtering guidance. It doesn't explain pagination, but the schema includes page_token descriptions. It lacks explicit comparison to sibling tools, but the content (trade, quote, IV, greeks) helps differentiate. Overall adequate for a complex tool.

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

Parameters4/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 adds value by highlighting the most relevant filter parameters (type, strike_price_gte/lte, expiration_date, limit) and their purpose in narrowing results. This gives the agent actionable guidance beyond schema descriptions.

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 'Retrieves option chain data for an underlying symbol' with a specific verb and resource, listing included data (trade, quote, IV, greeks). This distinguishes it from sibling tools like get_option_contract or get_option_snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It does not explicitly name alternative tools, but it provides clear context for when filtering is needed ('The response can be very large. Use the type... parameters to narrow results'). This implies usage for broad chain queries but lacks explicit exclusion or alternative references.

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/bartest5/alpacahq_alpaca-mcp-server'

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