Skip to main content
Glama

SN Data by Shikshan Nivesh

Short interest

get_short_interest
Read-onlyIdempotent

Every FINRA short interest settlement for the company, newest first: shares short, percent change from the last count, average daily volume and days to cover.

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": "get_short_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on or before this date (year-month-day).
fromNoOnly rows on or after this date (year-month-day).
limitNoMost rows to return, newest first. Default 24.
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/closed-world, so the description's contribution is the return shape — shares short, percent change from prior count, average daily volume, days to cover — which matters because there is no output schema. It doesn't mention update cadence limits or empty-result behavior, so not a 5.

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?

One dense sentence, no filler, with the resource and ordering front-loaded and the returned fields enumerated after. Every clause carries information.

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?

With no output schema, describing the returned metrics is exactly the missing piece, and ordering plus company scoping are covered. The only gap is settlement cadence/edge cases (e.g. no short interest reported for some tickers), which would help an agent interpret sparse results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so from/to/limit/ticker are already fully documented. The description only reinforces the 'newest first' ordering, which the limit description also states; it adds no format or filtering semantics beyond the schema.

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?

States a specific resource ('Every FINRA short interest settlement for the company') with scope and ordering ('newest first'), which is distinct from any fund/insider/holder sibling. It doesn't explicitly contrast with a named alternative, so it stops short of 5.

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

Usage Guidelines3/5

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

Usage is implied by the resource itself — an agent asking for short interest data would pick this. There is no explicit when-to-use/when-not statement and no reference to a sibling for related data (e.g. insider or holder tools), leaving the choice to inference.

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