list_nse_indicesRetrieve names of NSE/NIFTY indices available for constituent data. Use this tool to identify which index lists can be requested from the server.
Names of the NSE/NIFTY indices whose constituents this server can return.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering safety and mutability. The description adds the useful context that the returned names are limited to indices whose constituents the server can return, but it does not describe response format, ordering, or potential emptiness.
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?
The description is a single, efficient sentence that leads with the resource and directly states what the tool returns. No unnecessary words or filler.
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?
For a parameterless discovery tool with strong annotations, the description is complete. It tells the agent exactly what the tool returns and why that matters: indices whose constituents this server can support. No output schema exists, but the description adequately describes the return content.
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?
The tool has zero parameters and the schema description coverage is 100%, so there is no parameter documentation burden. The baseline of 4 applies because no parameter semantics are needed.
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 tool returns names of NSE/NIFTY indices, which is a specific resource and scope. It doesn't explicitly name a sibling tool, but the phrase 'whose constituents this server can return' distinguishes it from nse_index_constituents, which likely returns the constituents themselves.
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?
The description implies the tool is a discovery endpoint for enumerating supported indices before requesting constituents, but it doesn't explicitly say when to use it or when to prefer an alternative. There are no stated exclusions or direct references to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.