Skip to main content
Glama
mcp-india-stack

mcp-india-stack

get_stock_history

Read-onlyIdempotent

Fetch historical end-of-day stock data for an Indian ticker by symbol and optional period to analyze past price performance.

Instructions

[Experimental] Fetch historical end-of-day data for a given Indian stock ticker.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoTime period to fetch data for. Valid periods: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max1mo
symbolYesStock symbol/ticker to fetch. Examples: RELIANCE.NS, INFY.NS

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds two genuinely non-redundant facts: results are end-of-day granularity (not intraday) and the tag is experimental, implying possible instability. It does not disclose data source, latency, or what an invalid/unknown symbol returns.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the experimental caveat sits at the start where it will be seen. It is arguably too terse for the gaps it leaves, but nothing in it is wasted.

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 and annotations plus a 100%-covered parameter schema carry most of the load, so the description need not explain return shapes. Still, for a market-data tool it says nothing about symbol suffix requirements, empty-result behavior, or how '1d' interacts with end-of-day data, leaving the agent slightly under-informed.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (symbol and period, including the full period enum list) are already fully documented in the schema. The description only adds the qualifier 'Indian stock ticker', which is marginally useful context but no syntax or format detail beyond the schema examples (RELIANCE.NS, INFY.NS). Baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: 'Fetch historical end-of-day data' for 'a given Indian stock ticker.' This is clearly distinguishable from the sibling get_stock_quote (current price vs. historical EOD series), though it does not name that sibling explicitly.

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 or when-not-to-use guidance and no alternatives referenced. An agent must infer that this is for time-series lookups rather than live quotes purely from the words 'historical' and 'end-of-day'; the '[Experimental]' tag hints at reliability concerns but never says what to do about them.

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

Deploy Server

Other Tools