Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Daily Short Volume (FINRA Reg SHO off-exchange short-sale volume)

short_volume
Read-onlyIdempotent

Daily short-sale volume for a stock from FINRA's Reg SHO files (Console's daily short volume). Returns, per trading day, short volume, short-exempt volume, FINRA total volume and the short ratio (short / total), plus volume-weighted short ratios over the last 5 days, 20 days and 1 year (252 trading days), and the z-score of the last 5 days' average daily ratio against the past year.

What this is not: it covers off-exchange, FINRA-reported volume only, not total consolidated volume, and it is not short interest. A high short ratio is normal (market makers sell short to fill buy orders), so read it against the stock's own history (the z-score), not as a level. For shares held short, use short_interest.

Symbols follow FINRA: class shares use a slash (BRK/B); BRK.B and BRK-B are converted. About 400 days of history are kept. Some volumes in the source carry fractional shares (under review by FINRA's data team), so treat them as approximate.

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": {
      "ticker": "<ticker>"
    },
    "name": "short_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDaily rows to return, newest first (default 30, max 400). Ratios always use the full window.
tickerYesStock symbol (e.g. GME, TSLA, BRK/B or BRK.B).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds substantive behavior beyond them: ~400 days of retained history, the symbol-class normalization rules (BRK/B, BRK.B, BRK-B), and a known data-quality caveat that some source volumes carry fractional shares and should be treated as approximate.

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-loads the core purpose and uses a clear "What this is not" section to organize caveats, with no filler sentences. It is dense and fairly long, but each clause (coverage limits, ratio interpretation, symbol rules, history depth, fractional-share caveat) carries distinct information, so little could be cut without losing value.

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?

There is no output schema, yet the description fully describes the return columns, aggregation windows, and derived statistics, so an agent knows what it will receive. Combined with the history depth, caveats, and symbol rules, nothing material for correct invocation is missing.

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 documents days (default 30, max 400) and the full-window ratio behavior, so the baseline would be 3. The description earns above baseline by adding ticker format semantics — FINRA slash convention for class shares and the automatic conversion of BRK.B and BRK-B — which the schema only hints at via an example.

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?

Names a specific verb and resource ("Daily short-sale volume for a stock from FINRA's Reg SHO files") and enumerates the returned fields: short volume, short-exempt volume, total volume, short ratio, 5/20/252-day VW ratios, and a z-score. It explicitly distinguishes itself from short_interest and from consolidated volume, so an agent can separate it from the sibling tool without opening a schema.

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

Usage Guidelines5/5

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

Provides both a when-not (off-exchange FINRA volume only, not consolidated volume, not short interest) and a named alternative ("For shares held short, use short_interest"). It also gives interpretation guidance — read the ratio against the stock's own z-score rather than as an absolute level — which steers correct usage, not just selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources