Skip to main content
Glama
Sign In
NSE-MCP

NSE-MCP

by icharshal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_short_selling

Retrieve short-selling data for NSE stocks, including shares sold short and covering quantities. Filter by symbol or get top stocks by short-sold volume.

Instructions

NSE short-selling data — quantity of shares sold short and second-leg (covering) quantities, as reported by brokers under SEBI's short-selling framework.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_short_selling"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoReturn top N stocks by short-sold quantity. Omit for all.
symbolNoFilter by NSE symbol. Omit for all stocks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It mentions the data source and reporting framework but does not disclose behavioral traits such as data recency, update frequency, or any limitations (e.g., historical depth).

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?

The description is a single, well-constructed sentence that efficiently conveys the tool's purpose and data source without any superfluous words.

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?

Given the tool's simplicity (two optional parameters, no output schema) and the context of 17 sibling tools, the description provides sufficient information for an AI agent to understand the tool's role. However, it could be more complete by noting the absence of time periods or units.

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% with descriptions for both parameters. The description adds minimal extra meaning beyond the schema, stating that 'limit' returns top N by short-sold quantity and 'symbol' filters by NSE symbol. This is adequate but does not significantly enhance understanding.

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 clearly identifies the tool as providing NSE short-selling data, including quantity of shares sold short and second-leg covering quantities, as reported under SEBI's framework. This is specific and distinguishes it from sibling tools like search_by_symbol, get_quote, and get_top_gainers.

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?

The description does not explicitly state when to use this tool versus alternatives. It implies it is for accessing short-selling data but provides no guidance on scenarios where other tools might be more appropriate.

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

Deploy Server

Other Tools