TipRanks

get_options_contract

Read-onlyIdempotent

Snapshot one OCC contract — price, OI, intraday OHLCV, last trade.

The contract_ticker is an OCC-format symbol like 'O:AAPL260520C00205000'
(O: + underlying + YYMMDD + C/P + strike-in-thousandths-8-digits).
The 'O:' prefix is optional.

Quotes are typically delayed ~15 minutes. Greeks and implied
volatility are not available from this data source.

Args:
    contract_ticker: OCC contract symbol.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`contract_ticker`	Yes	OCC-format option ticker, e.g. 'O:AAPL260520C00205000'. The 'O:' prefix is optional.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful behavioral context: 'Quotes are typically delayed ~15 minutes' and 'Greeks and implied volatility are not available from this data source,' which are not in the annotations and help set expectations.

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 well-organized: a one-sentence summary followed by necessary formatting details and behavioral caveats, then a simple Args line. Every sentence carries meaningful information, with no fluff or repetition.

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

Completeness5/5

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

For a single-parameter tool with no output schema, the description is complete. It states what data is returned, how to format the parameter, and what limitations exist (delayed quotes, no Greeks/IV). This gives an agent all the context needed to select and invoke the tool correctly.

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

Parameters5/5

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

Although the schema already documents the contract_ticker parameter, the description adds deep semantic value by breaking down the OCC symbol format ('O: + underlying + YYMMDD + C/P + strike-in-thousandths-8-digits') and noting that the 'O:' prefix is optional. This goes beyond the schema's simple example and is essential for correctly constructing the ticker.

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 opens with 'Snapshot one OCC contract — price, OI, intraday OHLCV, last trade,' which uses a specific verb and resource and lists the returned data fields. This clearly distinguishes it from sibling tools like get_options_chain (which covers a chain) and get_options_expirations (which covers expirations).

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

Usage Guidelines3/5

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

The description implies usage for a single contract snapshot ('Snapshot one OCC contract') but never explicitly contrasts it with alternatives such as get_options_chain or get_options_unusual_trades. There is no when/when-not guidance, making the usage context clear but not explicit.

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

All TipRanks 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.8/5.0

Disambiguation3/5

Many tools have overlapping purposes, e.g. get_etf_analysis vs get_etf_forecast both provide ETF analyst consensus, get_etf_holdings vs get_etf_top_stocks both list constituents, and get_portfolio_overview vs get_portfolio_performance both return returns/performance. The detailed descriptions help, but the sheer number of similar tools creates ambiguity in selection.

Naming Consistency4/5

The set is largely consistent with a 'get_' prefix and descriptive nouns (get_stock_quotes, get_crypto_quote, get_dividend_history). Minor deviations include 'list_my_portfolios' instead of 'get_my_portfolios' and singular/plural variants like get_all_commodities_quotes vs get_commodity_quote, but the pattern remains predictable.

Tool Count1/5

With 71 tools, the count far exceeds the 50+ threshold described as an extreme mismatch. Even though the server covers a broad financial domain, such a large surface is overwhelming for an agent and includes many redundant or highly specific tools that could be consolidated.

Completeness5/5

The tool set provides comprehensive coverage of TipRanks data: quotes and historical data for all major asset classes, news, earnings and economic calendars, analyst and sentiment data, financial statements, technical analysis, options, portfolios, and screeners. There are no obvious dead ends for typical financial research tasks.

Resources

Need Help?