Fetch the current level of key Indian indices such as Nifty 50, Sensex, Bank Nifty, Nifty IT, or India VIX for market checks and assistant responses.
Latest level of an Indian index: nifty50, sensex, banknifty, niftyit or indiavix.
| Name | Required | Description | Default |
|---|---|---|---|
| index | No | nifty50 |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. Saying 'Latest level' usefully signals a current snapshot rather than a time series, but it says nothing about data freshness (live vs delayed), rate limits, or failure behavior when an invalid index is supplied.
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, then the enumeration. No wasted words.
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 described, and the parameter values are fully enumerated. Only the data-freshness and default-value details are missing, which are small for a single-parameter lookup tool.
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 coverage is 0% and the 'index' property has no enum or description, so the description must compensate — and it does by listing the five accepted values, which is exactly what the agent needs. It doesn't mention the 'nifty50' default, a minor omission.
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?
States a specific verb (return latest level) and resource (Indian index), and enumerates the five supported indices. The resource noun separates it from get_stock_quote and get_scheme_quote, though it never explicitly says so.
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?
Usage is only implied: the tool is evidently for fetching a current index snapshot, and the valid values are given. There is no explicit when-to-use, no exclusion of historical data (unlike get_stock_history/get_nav_history), and no mention of alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.