OptionsBell Options Flow

Unusual options activity

get_unusual_activity

Contract-level unusual options activity scan across 7,000+ US stocks (the dataset behind OptionsBell alerts). Filter by symbols, side and thresholds: Vol/OI ratio, premium (USD), IV, days-to-expiration, volume, open interest. Rows include strike, expiry, volume, open interest, IV, delta, sector and an estimated premium. Use for questions like 'what unusual put buying hit TSLA today?'

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_unusual_activity"
  }
}

Input Schema

Name	Required	Description
`raw`	No	true = skip the always-on base floor (Vol/OI>=1.5, OI>=100, premium>=$25k).
`date`	No	Trading day, YYYY-MM-DD. Defaults to the latest available day.
`type`	No	Side: c = calls, p = puts (default all).
`limit`	No	Max rows (default 300).
`since`	No	ISO-8601 timestamp; only contracts last seen intraday at or after this time (for polling).
`min_iv`	No	Minimum implied volatility in percent, e.g. 60.
`min_oi`	No	Minimum open interest.
`offset`	No	Rows to skip for paging; the response reports filtered_total and has_more.
`date_to`	No	Range end, YYYY-MM-DD inclusive.
`max_dte`	No	Maximum days to expiration, e.g. 30.
`symbols`	No	Comma-separated tickers, e.g. 'AAPL,NVDA,TSLA'.
`date_from`	No	Range start, YYYY-MM-DD inclusive.
`min_voloi`	No	Minimum volume/open-interest ratio, e.g. 5.
`min_volume`	No	Minimum contract volume.
`min_premium`	No	Minimum estimated premium in USD, e.g. 250000.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 20, 2026

addedInput schema / properties / min_oi

Added value: +{
+  "description": "Minimum open interest.",
+  "type": "number"
+}

addedInput schema / properties / min_volume

Added value: +{
+  "description": "Minimum contract volume.",
+  "type": "number"
+}

addedInput schema / properties / raw

Added value: +{
+  "description": "true = skip the always-on base floor (Vol/OI>=1.5, OI>=100, premium>=$25k).",
+  "type": "boolean"
+}

addedInput schema / properties / since

Added value: +{
+  "description": "ISO-8601 timestamp; only contracts last seen intraday at or after this time (for polling).",
+  "type": "string"
+}

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Rows to skip for paging; the response reports filtered_total and has_more.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

First observedJul 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses several behaviors: the always-on base floor (Vol/OI>=1.5, OI>=100, premium>=$25k), the 'raw' parameter to skip it, the response fields (including filtered_total and has_more for paging), and the meaning of 'since' for intraday polling. This goes beyond a generic read tool, though it does not mention error handling or side effects (unlikely for a scan).

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?

The description is well-structured and front-loaded with purpose, then filters, output fields, and an example. It is slightly long but every sentence provides value; no filler or redundancy. It could be tightened but is appropriately detailed for a tool with 15 parameters.

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 the lack of an output schema, the description compensates by listing output row fields and pagination details (offset, has_more). It covers defaults (date, type, limit) and the base-floor behavior. It does not explicitly mention edge cases like no results or symbol requirements, but it is sufficiently complete for an agent to use the tool correctly in most scenarios.

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 description coverage is 100%, so baseline is 3. The description adds meaningful context beyond the schema by grouping filters (Vol/OI, premium, IV, DTE, volume, OI) and explaining the output rows (strike, expiry, IV, delta, sector, premium). It also clarifies the 'raw' parameter's role, which is not obvious from the schema alone.

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 it is a contract-level unusual options activity scan across 7,000+ US stocks, listing specific filters and output fields. It also provides an example question ('what unusual put buying hit TSLA today?'), making its purpose unmistakable and distinguishing it from sibling tools like get_flow_history or get_top_prints by its focus on unusual activity thresholds.

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?

The description gives a clear usage context with an example question and explains the available filters, implying when to use it. However, it does not explicitly mention when not to use it or name alternative sibling tools, so it falls short of full routing guidance.

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

All OptionsBell Options Flow 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.