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 IV: the results carry price, OI, OI change, volume, day OHLC
and last_trade_date; delta/gamma/theta/vega, implied volatility and
bid/ask are not part of this data. When the user asks for them, call
this tool, present what it returns, and state plainly that those fields
are unavailable. Report only values that appear in the results, and
leave greeks and IV unestimated, including rules of thumb.

Args:
    contract_ticker: OCC contract symbol.

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": {
      "contract_ticker": "<contract_ticker>"
    },
    "name": "get_options_contract"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_options_contractOutput",
-  "type": "object"
-}New value: +null

First observedJul 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the annotations (which only declare readOnly/idempotent) by disclosing ~15-minute quote delay and an exact field-coverage boundary — no greeks, no IV, no bid/ask. It further instructs the agent to leave those values unestimated, which is real behavioral guidance that prevents hallucination.

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?

Front-loaded with the purpose and the key field, then format, then caveats. The greeks paragraph is long but earns its place by heading off a common failure mode; structure is easy to scan.

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?

With no output schema, the description takes on the burden of describing the return surface and does so concretely (price, OI, OI change, volume, day OHLC, last_trade_date). Combined with the delay and field-absence notes, an agent has everything needed to call and report correctly.

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 schema already gives the example plus the optional 'O:' prefix. The description adds value by decomposing the OCC format (YYMMDD, C/P, strike-in-thousandths-8-digits), giving the agent a way to validate or construct tickers beyond a single sample.

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 verb and resource ('Snapshot one OCC contract') and enumerates exactly what is returned (price, OI, intraday OHLCV, last trade). The word 'one' implicitly scopes it against the sibling get_options_chain, which returns many contracts.

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?

Gives an explicit conditional directive: when a user asks for greeks/IV, call this tool, present what it returns, and state the fields are unavailable. It lacks explicit routing versus get_options_chain or get_options_expirations, but the usage context is clear.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?