Skip to main content
Glama

OptionsBell Options Flow

by com.optionsbell
OverviewDiscussionsAdmin

Flow sentiment (Pro)

get_flow_sentiment

Bullish/bearish classification of each symbol's unusual flow with a 0-9 strength score, based on call/put volumes, premium and net delta. Pass a symbol for that ticker's sentiment time series (date_from, date_to, limit apply); omit it for the cross-market snapshot (filterable by sector, side, minimum strength or premium).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoTrading day, YYYY-MM-DD. Defaults to the latest available day.
sideNoOnly rows classified with this signal side (snapshot only).
limitNo
offsetNoSnapshot only. Rows to skip for paging; the response reports filtered_total and has_more.
sectorNoGICS sector name, e.g. 'Information Technology' (snapshot only).
symbolNoSingle ticker for its sentiment series; omit for the market-wide snapshot.
date_toNoRange end, YYYY-MM-DD inclusive.
symbolsNoComma-separated tickers, e.g. 'AAPL,NVDA,TSLA'.
date_fromNoRange start, YYYY-MM-DD inclusive.
min_premiumNoMinimum call+put premium in USD (snapshot only).
signal_onlyNoOnly rows with an active bullish/bearish signal (snapshot only).
min_strengthNoSnapshot only; rows without a signal count as 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / min_strength / description
      Previous value: -"Snapshot only."New value: +"Snapshot only; rows without a signal count as 0."
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Snapshot only. Rows to skip for paging; the response reports filtered_total and has_more.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / min_premium
      Added value: +{
+  "description": "Minimum call+put premium in USD (snapshot only).",
+  "type": "number"
+}
    • addedInput schema / properties / min_strength / description
      Added value: +"Snapshot only."
    • changedInput schema / properties / sector / description
      Previous value: -"GICS sector name, e.g. 'Information Technology'."New value: +"GICS sector name, e.g. 'Information Technology' (snapshot only)."
    • addedInput schema / properties / side
      Added value: +{
+  "description": "Only rows classified with this signal side (snapshot only).",
+  "enum": [
+    "bullish",
+    "bearish"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / signal_only / description
      Previous value: -"Only rows with an active bullish/bearish signal."New value: +"Only rows with an active bullish/bearish signal (snapshot only)."
  3. First observed

TDQS

A4.1/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 disclosure burden. It explains the scoring basis (call/put volumes, premium, net delta), the strength scale, and the two distinct response modes. It does not discuss pagination or edge cases, but those details are partially covered by schema parameter descriptions and there is no contradiction.

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 two dense sentences with no filler. It front-loads the core classification semantics, then explains the mode switch and filters in the second sentence. Every phrase earns its place.

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 12-parameter tool with high schema coverage and no output schema, the description conveys the essential purpose and the central mode-selection logic that would be hardest to infer. It omits the symbols and signal_only parameters, but the schema descriptions cover those, and the overall calling pattern is clear.

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 high, so the description's main job is to add selection semantics. It adds the crucial conditional: presence or absence of the symbol parameter switches between time-series and snapshot mode, and it groups the filter parameters cohesively. It does not enumerate every parameter, but the schema already documents those.

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 names the resource ('unusual flow') and the core output: a bullish/bearish classification with a 0-9 strength score, based on call/put volumes, premium, and net delta. It clearly explains the two modes, single-symbol time series vs cross-market snapshot. However, it does not explicitly contrast itself with sibling tools such as get_symbol_flow or get_sector_flow.

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 explicit conditional instructions: pass a symbol for the ticker's sentiment series, omit it for the snapshot, and filter the snapshot by sector, side, minimum strength, or premium. This is clear usage context, though it does not state when to prefer this tool over nearby siblings like get_symbol_flow or get_sector_flow.

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