FinanceKit MCP

options_chain

Read-only

Retrieve options chain for any stock, including calls and puts with expirations, strikes, volumes, open interest, implied volatility, and greeks.

Instructions

Get options chain (calls and puts) for a stock.

Returns available expirations and, if one is specified or the nearest is used, the full chain with strikes, volumes, open interest, implied volatility, and greeks (when available).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "options_chain"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Stock ticker (e.g., 'AAPL')
`expiration`	No	Optional expiration date YYYY-MM-DD, or leave empty for nearest

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0May 1, 2026
Removedv1.2.0May 1, 2026
First observedv0.1.0Apr 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds valuable behavioral context: it returns available expirations and, if specified, a full chain with strikes, volumes, open interest, implied volatility, and greeks. This goes beyond the annotation.

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, front-loaded with the main action, and no wasted words. Each sentence contributes essential information.

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?

With an output schema present (inferred from context), the description covers the core functionality: retrieving expirations and option chain details. It could mention pagination or data availability, but overall it is sufficient for a simple read-only 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%, and the description clarifies behavior: leaving expiration empty uses the nearest date. It also mentions that the tool first returns available expirations, which is not in the schema. This adds meaningful context.

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 'Get options chain (calls and puts) for a stock', using a specific verb and resource. It distinguishes from sibling tools (e.g., stock_quote, price_history) by focusing exclusively on options data.

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. For instance, it does not mention that stock_quote should be used for current price queries or that price_history is for historical prices. Agents must infer usage from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server