Fintel Discovery — Financial Intelligence for AI Agents

Get Options Chain (Calls & Puts)

GetOptionsChain

Read-onlyIdempotent

    Fetch the full options chain (calls and puts) for one expiry date.
    Returns strike price, bid, ask, last price, implied volatility, open
    interest, and volume for every contract.

    Use this tool when:
    - You are researching options strategies for a stock or ETF
    - You need implied volatility across strikes for a specific expiry
    - You want to see open interest to gauge market sentiment

    Call GetOptionsExpirations first to get valid expiry dates.
    If expiry_date is omitted, returns the nearest available expiry.

    Source: Yahoo Finance via yfinance. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds relevant context by stating the data source (Yahoo Finance via yfinance), that no API key is required, and how missing expiry_date resolves. It does not address latency or data limitations, but those are secondary given the annotations.

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 compact, front-loaded with the core behavior, and uses short bullets for usage conditions. Every sentence adds useful information, and the source/API-key note is placed last without bloating the text.

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?

For a read-only fetch tool with an output schema, the description covers what the tool returns, how to get valid expiry dates, and external source requirements. It could be slightly more explicit about symbol being required despite the schema marking it optional, which would make an agent less likely to call it without required context.

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 description clarifies the behavior of expiry_date (nearest available expiry when omitted) and identifies symbol examples, which adds some semantic guidance. However, schema description coverage is 0% and the description does not explicitly state that symbol must be supplied, nor does it discuss the other schema fields (e.g., mcp_prompt_id, question_asked, source_resource_id). The nested schema is rich, but the description itself leaves a notable gap.

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?

States a specific action ('Fetch the full options chain') with a clear resource (calls and puts for one expiry), and enumerates the returned fields. The phrase 'one expiry date' and the mention of a companion tool help distinguish it from GetOptionsExpirations and other market-data siblings.

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

Usage Guidelines5/5

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

Provides explicit 'Use this tool when' conditions and a concrete prerequisite ('Call GetOptionsExpirations first to get valid expiry dates'). It also gives a fallback behavior for omitted expiry_date, giving an agent clear decision rules for invocation.

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

All Fintel Discovery — Financial Intelligence for AI Agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a distinct resource and action, with clear separation between search and detail tools (e.g., SearchIAPDFirm vs GetIAPDFirmDetail, SearchBrokerCheck vs GetBrokerCheckDetail). A few pairs like SearchBrokerCheck and SearchBrokerCheckFirm could cause momentary confusion, but descriptions clarify individual vs firm scope.

Naming Consistency4/5

The dominant pattern is consistent: Search* for discovery, Get* for retrieval, with CamelCase throughout. Minor deviations like LookupTicker and MapInstrumentIds introduce different verbs, and SearchBrokerCheck does not explicitly signal 'individual' unlike SearchBrokerCheckFirm, but the overall convention remains predictable.

Tool Count2/5

With 32 tools, the surface is quite heavy and exceeds the 25+ threshold for 'too many.' While the financial intelligence domain is broad, several search/detail pairs and overlapping data-source tools could be consolidated to reduce cognitive load for agents.

Completeness4/5

The toolset covers major workflows well: 13F holdings, fund fee comparison, advisor due diligence, macro data, price history, options, and identifier mapping. Minor gaps exist, such as no standalone real-time quote tool, no news/sentiment data, and no direct CUSIP-to-company-name search, but these are workable around.

Resources

Need Help?