Skip to main content
Glama

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

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 (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: 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.

  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.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), but the description adds real behavioral context the annotations cannot: the FINRA 999.99 days-to-cover cap, that capped rows are a sentinel ranked last, why they occur (tiny average-daily-volume denominator), and how to filter them out. The bi-monthly settlement cadence also tells the agent how stale the data may be.

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?

Front-loaded with what the tool returns, followed by the sentinel caveat and the filter workaround, then sibling routing. Semicolon-packed but every sentence carries distinct decision-relevant information; nothing is padding.

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, and the description partly compensates by naming the granularity and the sortable fields (daysToCover, shortPosition, change). Pagination mechanics live in the schema's offset description. Row-level fields beyond the sort keys are still unspecified, which is the only real gap for a no-output-schema tool.

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 a baseline of 3 applies, but the description adds meaning beyond the schema by explaining the rationale behind minAvgDailyVolume (dropping illiquid names whose days-to-cover is inflated) and by tying sortBy's daysToCover key to the sentinel-last ranking behavior.

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 (market-wide snapshot of the latest FINRA bi-monthly short interest settlement), the row granularity, and the default ordering. It explicitly names the siblings it is not — GetShortSqueezeScores, GetShortInterest, GetShortVolume — so an agent can discriminate without opening schemas.

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?

Gives explicit routing rules: use GetShortSqueezeScores for squeeze-candidate ranking, GetShortInterest for a single stock/ETF history, GetShortVolume/GetLargestShortVolume for daily short-sale flow. It also states when to set minAvgDailyVolume to exclude illiquid names, which is actionable guidance rather than a restatement.

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