Skip to main content
Glama
darved2305

groww-mcp

by darved2305

get_fund_details

Retrieve mutual fund details including NAV, AUM, expense ratio, returns, and risk grade using the fund's ISIN code to analyze investment performance.

Instructions

NAV, AUM, expense ratio, returns (1y/3y/5y), risk grade for a mutual fund

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isinYesMutual fund ISIN code, e.g. INF846K01EW2

Implementation Reference

  • The 'get_fund_details' tool is registered here and includes the handler logic that fetches fund details using 'growwClient.getFundDetails(isin)' and formats the output.
    server.tool(
      "get_fund_details",
      "NAV, AUM, expense ratio, returns (1y/3y/5y), risk grade for a mutual fund",
      {
        isin: z.string().describe("Mutual fund ISIN code, e.g. INF846K01EW2"),
      },
      async ({ isin }) => {
        try {
          const f = await growwClient.getFundDetails(isin);
          const stars = "⭐".repeat(Math.min(f.rating, 5));
    
          const riskLabel: Record<string, string> = {
            LOW: "🟢 Low",
            MODERATELY_LOW: "🟢 Moderately Low",
            MODERATE: "🟡 Moderate",
            MODERATELY_HIGH: "🟠 Moderately High",
            HIGH: "🔴 High",
          };
    
          const text = [
            `📈 ${f.name}`,
            `${"─".repeat(55)}`,
            `AMC:            ${f.amc}`,
            `Category:       ${f.category} > ${f.subCategory}`,
            `ISIN:           ${f.isin}`,
            `Rating:         ${stars}`,
            ``,
            `💰 KEY METRICS`,
            `NAV:            ${formatCurrencyExact(f.nav)}`,
            `AUM:            ${formatCurrency(f.aum)}`,
            `Expense Ratio:  ${f.expenseRatio}%`,
            `Risk:           ${riskLabel[f.riskGrade] || f.riskGrade}`,
            ``,
            `📊 RETURNS`,
            `1 Year:         ${formatPercent(f.returns1y)}`,
            `3 Year:         ${formatPercent(f.returns3y)}`,
            `5 Year:         ${formatPercent(f.returns5y)}`,
            ``,
            `💳 INVESTMENT`,
            `Min Lumpsum:    ${formatCurrencyExact(f.minInvestment)}`,
            `Min SIP:        ${formatCurrencyExact(f.minSIPAmount)}`,
            `Exit Load:      ${f.exitLoad}`,
            ``,
            `As of ${nowIST()}`,
          ].join("\n");
          return mcpText(text);
        } catch (err) {
          return mcpError(normalizeError(err));
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what data is returned but lacks critical behavioral details: whether this is a read-only operation (implied but not stated), if it requires authentication, rate limits, error handling (e.g., invalid ISIN), or data freshness. For a tool with zero annotation coverage, this is a significant gap.

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 extremely concise and front-loaded, listing all key metrics in a single, efficient phrase without unnecessary words. Every element (NAV, AUM, etc.) directly contributes to understanding the tool's output, making it zero waste and highly structured.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally complete. It specifies what data is retrieved but lacks behavioral context (e.g., safety, errors) and doesn't explain return values (since no output schema exists). For a simple lookup tool, it's adequate but has clear gaps in transparency.

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?

The schema description coverage is 100%, with the single parameter 'isin' well-documented in the schema. The description doesn't add any parameter-specific semantics beyond implying it's for mutual funds (which the schema's example also suggests). With high schema coverage and only one parameter, the baseline is 3, but the description's clarity on the resource type slightly enhances understanding, warranting a 4.

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 clearly states the specific verb ('get') and resource ('fund details'), listing exactly what metrics are retrieved (NAV, AUM, expense ratio, returns, risk grade) for a mutual fund. It distinguishes from siblings like 'search_funds' (which likely searches) or 'invest_in_fund' (which transacts), making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid ISIN), exclusions (e.g., not for stocks), or direct comparisons to siblings like 'search_funds' (which might return basic info) or 'get_quote' (which might be for stocks). Usage is implied by the name but not explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/darved2305/groww-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server