Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Mutual Fund NAV History

get_mutual_fund_nav_history
Read-onlyIdempotent

Daily NAV history of one mutual fund plan by scheme code (INR per unit, from as early as 1986). Long ranges return period-end NAVs (weekly, monthly or quarterly) so the series fits; interval forces one (newest 300 points at most).

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": {
      "scheme_code": "<scheme_code>"
    },
    "name": "get_mutual_fund_nav_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD; default the latest NAV. A holiday gives the last NAV before it.
fromNoYYYY-MM-DD; default one year before `to`.
intervalNoSampling; default: the finest that fits.
scheme_codeYesScheme code, e.g. "122639".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM-DD; default the latest NAV."New value: +"YYYY-MM-DD; default the latest NAV. A holiday gives the last NAV before it."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add operational detail — and it does: long ranges are silently converted to period-end NAVs, `interval` overrides that automatic sampling, and results are capped at the newest 300 points. The only omission is what the returned series looks like, which matters somewhat for a no-output-schema tool.

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?

Two tight sentences with the core capability front-loaded and the sampling caveat second. Dense but every clause carries information; only the slightly informal 'so the series fits' is filler-ish.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read tool with full schema coverage and annotations, the description covers scope, units, history depth, and the downsampling/cap behavior that would otherwise surprise an agent. Missing only a brief note on the returned series shape, which is not covered by an output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that the default interval is the finest that fits the requested range and that an explicit `interval` forces that granularity subject to the 300-point cap. That clarifies the interaction between `from`/`to` and `interval`, which the schema documents only in isolation.

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+resource: daily NAV history for a single mutual fund plan keyed by scheme code, with units (INR per unit) and historical depth (from 1986). It is clearly narrower than a general fund-lookup sibling, though it never names an alternative tool outright.

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

Usage Guidelines3/5

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

The use case (pull a historical NAV series for one scheme) is implied rather than stated, and there is no explicit when-to-use/when-not guidance versus siblings like get_mutual_fund or get_price_history. The note that long ranges are auto-downsampled is useful context but is behavioral, not routing, guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.