Indian Stock Exchange API2 MCP Server

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

With no annotations provided, the description carries the full disclosure burden. It mentions the GET method and 'latest' data (implying real-time/recent), but lacks critical behavioral details: rate limits, what constitutes 'most active' (top N count?), pagination behavior, market hours relevance, or safety guarantees. The truncated example response is cut off mid-JSON, reducing utility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Markdown formatting with endpoint/method headers adds structural clarity but also verbosity. The core description is one clear sentence. However, the included example response is truncated/malformed (ending with escaped quotes), which wastes space and creates visual noise without adding value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a zero-parameter retrieval tool. It identifies the exchange (NSE) and metric (volume), but given the lack of output schema, the truncated example JSON could have provided critical field documentation if complete. Missing operational context like data freshness guarantees or rate limiting.

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

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

Input schema has zero parameters (100% coverage trivially satisfied). The description correctly implies this is a parameterless fetch operation requiring no filters, meeting the baseline expectation for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Get), resource (most active stocks), and scope (NSE based on trading volume). It implicitly distinguishes from sibling 'bse_most_active' by specifying the National Stock Exchange, though it doesn't explicitly differentiate from 'get_trending_stocks' or 'price_shockers'.

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

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

No explicit guidance on when to use this tool versus siblings like 'bse_most_active' or 'get_trending_stocks'. While the NSE naming provides implicit context, there are no stated prerequisites or exclusion criteria for selection.

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