MarketPulse MCP

mutual_fund_nav

Get the latest NAV and details for any Indian mutual fund. Search by fund name or scheme code to view NAV, daily change, and 7-day history—no API key needed.

Instructions

Get the latest NAV and details for any Indian mutual fund.

Searches the AMFI database — no API key required.

Args: query: Fund name (e.g. "SBI Bluechip", "HDFC Flexi Cap") or numeric scheme code (e.g. "119598")

Examples: mutual_fund_nav("SBI Bluechip") → NAV, change, 7-day history mutual_fund_nav("Axis Long Term") → ELSS fund NAV mutual_fund_nav("119598") → Fetch by scheme code directly

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": {
      "query": "<query>"
    },
    "name": "mutual_fund_nav"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Aug 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the data source (AMFI database), states that no API key is required, and provides examples of return values (NAV, change, 7-day history). This goes beyond a minimal description, though it does not cover error cases or rate limits.

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

Conciseness5/5

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

The description is concise and well-structured. It front-loads the primary purpose, adds a brief note on the data source and authentication, and then presents clear args and examples. Every sentence contributes value.

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

Completeness5/5

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

For a tool with a single parameter and an output schema, the description is remarkably complete. It explains the input format, provides examples, states the data source, and hints at the return content (NAV, change, history). This leaves little ambiguity for an agent.

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

Parameters5/5

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

The input schema has a single 'query' parameter with zero description coverage. The description compensates fully by explaining that 'query' accepts either a fund name or a numeric scheme code, with concrete examples. This adds significant meaning beyond the schema.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Get the latest NAV and details for any Indian mutual fund.' It clearly differentiates from sibling tools like stock_quote by focusing on mutual fund NAV. The examples further reinforce the purpose by showing fund names and scheme codes.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: for any Indian mutual fund NAV lookup. It gives examples of valid queries, implying usage. However, it does not explicitly mention when not to use it or name alternatives, so it stops short of a 5.

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

Deploy Server