Skip to main content
Glama
darved2305

groww-mcp

by darved2305

invest_in_fund

Make a one-time lumpsum investment in a mutual fund by specifying the ISIN code and investment amount in INR.

Instructions

One-time lumpsum investment in a mutual fund

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isinYesMutual fund ISIN code
amountYesInvestment amount in INR

Implementation Reference

  • The tool 'invest_in_fund' is registered and implemented in 'src/tools/funds.ts' using the 'server.tool' method. It takes an ISIN and amount, validates the amount, and calls the 'growwClient.investInFund' method.
    // ── invest_in_fund ────────────────────────────────────────
    server.tool(
      "invest_in_fund",
      "One-time lumpsum investment in a mutual fund",
      {
        isin: z.string().describe("Mutual fund ISIN code"),
        amount: z.number().positive().describe("Investment amount in INR"),
      },
      async ({ isin, amount }) => {
        try {
          if (amount < 100) return mcpError("Minimum investment amount is ₹100");
    
          const result = await growwClient.investInFund({ isin, amount });
    
          const text = [
            `💰 INVESTMENT SUBMITTED`,
            `${"─".repeat(40)}`,
            `Transaction ID: ${result.transactionId}`,
            `Fund:           ${isin}`,
            `Amount:         ${formatCurrencyExact(amount)}`,
            `NAV:            ${formatCurrencyExact(result.nav)}`,
            `Est. Units:     ${result.units}`,
            `Status:         ${result.status}`,
            ``,
            `${result.message}`,
            ``,
            `⚠️ This is ${process.env.MOCK_MODE === "true" ? "a MOCK investment (no real money)" : "a REAL investment — money will be debited from your account"}`,
          ].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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an investment action, implying a financial transaction, but doesn't mention critical aspects like authentication requirements, whether this executes immediately or creates an order, potential fees, confirmation mechanisms, or what happens on failure. This leaves significant gaps for a tool that likely involves monetary transactions.

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 at just 5 words, front-loading the essential information with zero wasted words. Every element ('one-time', 'lumpsum', 'investment', 'mutual fund') contributes meaningfully to understanding the tool's purpose.

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

Completeness2/5

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

For a financial transaction tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after invocation (confirmation? order ID? error handling?), doesn't mention authentication or permission requirements, and provides no behavioral context about execution timing or limitations. Given the complexity and risk profile of investment tools, this leaves too many unanswered questions.

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%, with both parameters clearly documented in the schema itself (ISIN code and amount in INR). The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline but doesn't provide extra value like explaining ISIN format requirements or minimum investment amounts.

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 description clearly states the action ('one-time lumpsum investment') and resource ('mutual fund'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'place_order' or 'create_sip' which might also involve investment actions, leaving some ambiguity about when this specific tool should be used.

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 like 'place_order' (which might handle stocks) or 'create_sip' (for recurring investments). It mentions 'one-time' and 'lumpsum' which helps distinguish from SIPs, but offers no explicit when/when-not instructions or prerequisites for use.

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