Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Mutual Fund

get_mutual_fund
Read-onlyIdempotent

Indian mutual fund scheme by scheme code, ISIN or name (also old names, typos). A sure match returns the plan (fund, house, category, plan/option, ISINs, latest NAV), trailing and calendar-year returns from its NAVs, current expense ratio and its changes, the fund's profile (objective, benchmark, riskometer, exit load, minimums, managers), a fund-level snapshot (AUM, returns vs benchmark), risk or tracking figures where available, volatility, Sharpe and Sortino computed from NAVs, its latest portfolio month and other plans. Else ranked scheme codes, flagged when uncertain. A house's name adds its company, status and AUM history. Active and closed schemes; returns are in percent, 3y+ annualised.

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": "get_mutual_fund"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesScheme code, ISIN, or name as written, e.g. "parag flexi cap direct growth".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Scheme code, e.g. \"122639\", or up to 6 name words, e.g. \"parag flexi cap direct growth\"."New value: +"Scheme code, ISIN, or name as written, e.g. \"parag flexi cap direct growth\"."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real behavior: a confident match returns the full scheme bundle while anything else returns ranked scheme codes flagged as uncertain. It also states units and conventions ('returns are in percent, 3y+ annualised') and that both active and closed schemes are covered. The main omission is what happens on a total miss, and there is no pricing/rate-limit or payload-size context.

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?

The key matching semantics are front-loaded, which is good, but the middle sentence is a breathless comma-list of a dozen return fields ('...risk or tracking figures where available, volatility, Sharpe and Sortino...') that is hard to parse and would read far better as a structured list or trimmed to the headline items. Every element is arguably informative, but the packaging wastes the reader's attention.

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?

This is a single-parameter lookup with no output schema, so the description must carry the return-shape burden, and it does enumerate the returned content (plan details, NAV, returns, expense ratio, profile, AUM snapshot, risk metrics, portfolio month) plus the fallback path. For a read-only, one-argument tool that is close to sufficient; only the empty-result case is left unstated.

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?

With one parameter at 100% schema description coverage, the baseline is 3. The description does add genuine meaning the schema lacks - fuzzy matching of old names and typos, and the fact that a fund-house name changes the returned payload - but the long output enumeration competes for attention and the single `query` field's syntax is otherwise left to the schema example.

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?

The opening clause names the resource and the accepted key types precisely: 'Indian mutual fund scheme by scheme code, ISIN or name (also old names, typos)'. An agent knows exactly what is being looked up. It does not distinguish itself from siblings such as get_mutual_fund_nav_history, get_mutual_fund_portfolio or screen_mutual_funds, and the long enumeration of returned fields muddies rather than sharpens the core purpose.

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?

There is no explicit when-to-use / when-not / use-instead-this guidance, despite closely related siblings existing. What is present is input-form guidance: names and typos are tolerated and a house name widens the response to company data. That implies usage but leaves the agent to infer when this tool beats the NAV-history or portfolio siblings.

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.