Skip to main content
Glama

OptionsBell Options Flow

by com.optionsbell
OverviewDiscussionsAdmin

Multi-day unusual-flow streaks (Pro)

get_flow_streaks

Symbols with unusual options activity on N+ consecutive trading days, with the dominant side (call/put). Persistent unusual flow is a stronger signal than a single print - use for 'where does money keep showing up?'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoTrading day, YYYY-MM-DD. Defaults to the latest available day.
sideNoDominant side by C/P volume ratio.
limitNo
offsetNoRows to skip for paging; the response reports filtered_total and has_more.
symbolsNoComma-separated tickers, e.g. 'AAPL,NVDA,TSLA'.
min_streakNoMinimum consecutive days (default 3).
min_volumeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / min_streak / maximum
      Previous value: -9007199254740991New value: +365
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains the core output concept and the signal interpretation, but it does not disclose response shape, pagination behavior, or any limitations beyond what the schema states.

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 compact sentences: the first front-loads the core concept and output, the second adds actionable context without fluff. Every clause earns its place.

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

Completeness2/5

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

With no output schema, no annotations, and 7 parameters, the description leaves important gaps: no return-field details, no mention of defaults, and no explicit sibling differentiation. It covers the concept and use case but is not complete enough for fully autonomous invocation.

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

Parameters2/5

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

Schema coverage is 71%, leaving limit and min_volume without descriptions. The description adds no parameter-level meaning beyond mentioning the dominant side, which is already in the schema, so it fails to compensate for the undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (symbols with unusual options activity) and a clear differentiator: N+ consecutive trading days with a dominant call/put side. It does not name sibling tools, but the 'single print' contrast helps separate it from single-event flow tools.

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 phrase 'Persistent unusual flow is a stronger signal than a single print' and the use case 'where does money keep showing up?' give clear contextual guidance. However, it does not explicitly name alternative tools or state when not to use this tool.

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 toolsInspect
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