nse_get_index_quoteFetch a live NSE index snapshot such as NIFTY 50, NIFTY BANK, or NIFTY MIDCAP 100 to check current Indian market levels.
Get a live NSE index snapshot (NIFTY 50, NIFTY BANK, NIFTY IT, ...).
| Name | Required | Description | Default |
|---|---|---|---|
| index_name | No | Index name, e.g. 'NIFTY 50', 'NIFTY BANK', 'NIFTY MIDCAP 100'. | NIFTY 50 |
| 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?
No annotations exist, so the description carries the full burden. 'Live' hints at real-time data, but it says nothing about market-hours behavior, data staleness, rate limits, or whether the index_name must match an exact symbol — all material for a market-data call.
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?
One sentence, front-loaded with the verb and resource, zero filler. Appropriately sized for a single-parameter lookup.
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?
An output schema exists, so return values need not be explained, and the lone parameter is fully documented. The remaining gap is the unstated relationship to nse_get_quote and the lack of any market-data caveats.
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?
Schema description coverage is 100% and the single parameter is fully documented with a default and examples, so the baseline is 3. The description's parenthetical examples duplicate what the schema already lists rather than adding new meaning.
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?
Clear verb+resource: 'Get a live NSE index snapshot', with concrete index examples. It implies an index-level feed versus the sibling nse_get_quote (a security-level quote), but never states that distinction explicitly, so an agent must infer which to call.
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 when-to-use guidance, no prerequisites, and no mention of the closest alternative (nse_get_quote for stocks vs this for indices). Usage is only implied by the word 'index'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.