Skip to main content
Glama

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Largest Short Volume by Day

GetLargestShortVolume
Read-only

Get the exact listed securities, including ETFs, with the largest daily short sale volume for a single trading day (defaults to the latest available), from FINRA's daily short sale volume files, sorted by short volume descending. Short % is the share of that day's FINRA-facility (off-exchange/TRF) volume sold short — 40-50% is a normal market-making baseline — NOT short interest (the open short position; use GetShortInterest/GetShortInterestSnapshot for positions and GetShortSqueezeScores for operating-stock squeeze candidates; use GetShortVolume for one listed security's daily history). Pass sortBy=shortPercent with a minTotalVolume floor to rank by short intensity instead of raw size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoTrading day in YYYY-MM-DD format (defaults to the latest available day)
offsetNoNumber of ranked results to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached.
sortByNoSort key: shortVolume (default) or shortPercent — with shortPercent set a minTotalVolume floor, otherwise illiquid names dominateshortVolume
maxResultsNoMaximum number of results to return (default: 50, max: 500)
minShortVolumeNoMinimum short volume filter (default: 0)
minTotalVolumeNoMinimum total FINRA-reported volume filter, in shares (default: 0 = no floor)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offset / description
      Previous value: -"Number of ranked results to skip before returning rows — pass the previous call's last row number to page past the maxResults cap (default: 0)"New value: +"Number of ranked results to skip before returning rows (default: 0, clamped to 0-100000). For the next page, add the returned row count to the clamped current offset; if the next offset exceeds 100000, narrow the filters instead. Stop when fewer than the effective page size (maxResults clamped to 1-500) are returned, or the response's total has been reached."
  2. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of ranked results to skip before returning rows — pass the previous call's last row number to page past the maxResults cap (default: 0)",
+  "type": "integer"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine interpretive context beyond the annotations — that Short % is a share of FINRA TRF (off-exchange) volume with a 40-50% market-making baseline, and that it is not short interest — which materially improves correct interpretation.

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 scope, then the metric definition, then sibling routing and the sort recommendation. It is dense — a single long paragraph — but every sentence carries useful information with no filler.

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?

There is no output schema, but the description conveys what is returned (listed securities including ETFs ranked by short volume descending) and the metric's meaning. Combined with the full schema coverage, an agent has enough to invoke correctly; pagination behavior is carried by the schema, not the description.

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%, so the baseline is 3, but the description adds meaning beyond the schema for sortBy by explaining that shortPercent requires a minTotalVolume floor to avoid illiquid names dominating. Other params are fully documented in the schema, so no further compensation is needed.

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+resource (largest daily short sale volume securities for a single trading day), names the data source (FINRA daily short sale volume files), and the sort order. It explicitly distinguishes the metric from short interest and from sibling tools, so an agent can tell it apart from GetShortVolume/GetShortInterest 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?

Explicitly routes the agent: use GetShortInterest/GetShortInterestSnapshot for positions, GetShortSqueezeScores for squeeze candidates, and GetShortVolume for one security's history. It also states when to change to sortBy=shortPercent with a minTotalVolume floor to rank by intensity rather than raw size — clear when/when-not/alternative guidance.

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

All Equibles 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