Skip to main content
Glama
Indian Stocks MCP

Indian Stocks MCP

by Shubhampm18

get_index_history

Retrieve daily close history for Indian indices like Nifty and Sensex, using an as-of date and lookback window to support point-in-time analysis.

Instructions

Index close history (^NSEI, ^BSESN, ^NSEBANK …).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": "<index>"
    },
    "name": "get_index_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo
indexYes
lookback_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden and delivers almost nothing: no statement of read-only nature, defaults (lookback_days=90), what as_of controls, or whether missing/partial data is possible. Only the word 'history' hints that this is a read over past data.

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

Conciseness3/5

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

It is a single short fragment with no filler, and the ticker examples are the most useful part, but it is under-specified rather than genuinely concise. There is no front-loaded statement of what the call returns or how the parameters shape it.

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

Completeness3/5

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, which lowers the bar. Still, for a three-parameter time-series tool with zero schema coverage and no annotations, the description leaves an agent guessing about as_of, lookback semantics, and how this differs from get_ohlcv.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, and the description compensates only partially by illustrating the index symbol format. The semantics of as_of (date cutoff?) and lookback_days (window length?) remain entirely undocumented, leaving two of three parameters ambiguous.

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

Purpose3/5

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

The fragment 'Index close history' names the resource and the parenthetical ticker examples (^NSEI, ^BSESN, ^NSEBANK) show the index identifier format, but the verb is only implied and there is no differentiation from the sibling get_ohlcv, which plausibly also returns historical price data. An agent can guess the intent but cannot confidently distinguish scope.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusion of alternatives such as get_ohlcv or get_returns, and no mention of prerequisites like required index codes or data availability windows. The only implicit signal is that it applies to indices rather than individual stocks.

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