Skip to main content
Glama

equibles

by io.github.daniel3303

Market-Wide Short Interest Snapshot

GetShortInterestSnapshot
Read-only

Market-wide snapshot of the latest FINRA bi-monthly short interest settlement — one row per exact listed security, sorted by days to cover (descending) by default. FINRA caps days to cover at 999.99: capped rows are a sentinel (almost always illiquid names with a tiny average-daily-volume denominator) and are ranked after real readings; pass minAvgDailyVolume (e.g. 100000) to drop illiquid names entirely. This is the raw FINRA snapshot — for genuine short-squeeze candidate ranking use GetShortSqueezeScores; for one stock or ETF's history use GetShortInterest; for daily short-sale flow use GetShortVolume/GetLargestShortVolume.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of ranked results to skip before returning rows — pass the previous call's last row number to page past the maxResults cap (default: 0)
sortByNoSort key: daysToCover (default; FINRA-capped 999.99 sentinel rows ranked last), shortPosition, or change (largest increase in short position first)daysToCover
maxResultsNoMaximum number of results to return (default: 50, max: 500)
minDaysToCoverNoMinimum days to cover filter (default: 0)
minAvgDailyVolumeNoMinimum average daily share volume — set a floor (e.g. 100000) to drop illiquid names whose days-to-cover is inflated by a tiny volume denominator (default: 0 = no floor)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context: FINRA caps days to cover at 999.99, capped rows act as a sentinel, are ranked after real readings, and are almost always illiquid names. It also discloses the default sorting behavior and the existence of the cap. This goes well beyond the annotations.

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?

Three dense sentences, front-loaded with the core purpose, followed by the critical edge-case explanation, then the sibling routing. Every sentence earns its place: no filler, no repetition of schema content. The structure helps an agent quickly grasp scope, quirks, and alternatives.

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?

Given 5 optional parameters, no enums, no output schema, and a rich sibling context, this description is complete enough for correct selection and invocation. It covers the data source, granularity, default sort, sentinel cap, filtering guidance, and alternatives. The absence of an output schema is mitigated by the description's clarity on what the snapshot represents and the sort keys exposed in the schema.

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. The description adds interpretive value beyond the schema by explaining why minAvgDailyVolume matters (sentinel cap caused by tiny volume denominator) and how capped rows behave under sorting. It reinforces the offset paging concept implicitly via 'ranked results' but relies on the schema for exact parameter semantics. The added context justifies a 4.

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 uses a specific verb and resource: 'Market-wide snapshot of the latest FINRA bi-monthly short interest settlement'. It clearly distinguishes itself from sibling tools by naming GetShortSqueezeScores, GetShortInterest, GetShortVolume, and GetLargestShortVolume as alternatives for different use cases. The scope ('one row per exact listed security') and default sort order are explicit.

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?

The description provides explicit routing guidance: 'for genuine short-squeeze candidate ranking use GetShortSqueezeScores; for one stock or ETF's history use GetShortInterest; for daily short-sale flow use GetShortVolume/GetLargestShortVolume.' It also gives a concrete usage recommendation ('pass minAvgDailyVolume (e.g. 100000) to drop illiquid names entirely'). This is clear when-to-use and when-not-to-use 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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources