Skip to main content
Glama
darved2305

groww-mcp

by darved2305

create_sip

Set up a systematic investment plan (SIP) for mutual funds by specifying fund ISIN, investment amount, frequency, and start date.

Instructions

Create a new SIP with fund ISIN, amount, frequency, and start date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isinYesMutual fund ISIN code, e.g. INF846K01EW2
amountYesSIP amount in INR
frequencyNoSIP frequencyMONTHLY
start_dateYesSIP start date (YYYY-MM-DD)

Implementation Reference

  • The tool `create_sip` is registered here using `server.tool` and its implementation (handler) is defined in the same block.
    // ── create_sip ────────────────────────────────────────────
    server.tool(
      "create_sip",
      "Create a new SIP with fund ISIN, amount, frequency, and start date",
      {
        isin: z.string().describe("Mutual fund ISIN code, e.g. INF846K01EW2"),
        amount: z.number().positive().describe("SIP amount in INR"),
        frequency: z.enum(["MONTHLY", "WEEKLY", "QUARTERLY"]).default("MONTHLY").describe("SIP frequency"),
        start_date: z.string().describe("SIP start date (YYYY-MM-DD)"),
      },
      async ({ isin, amount, frequency, start_date }) => {
        try {
          if (amount < 100) return mcpError("Minimum SIP amount is ₹100");
    
          const result = await growwClient.createSIP({
            isin,
            amount,
            frequency,
            startDate: start_date,
          });
    
          const text = [
            `✅ SIP CREATED`,
            `${"─".repeat(40)}`,
            `SIP ID:    ${result.sipId}`,
            `Fund:      ${isin}`,
            `Amount:    ${formatCurrencyExact(amount)} / ${frequency.toLowerCase()}`,
            `Starts:    ${start_date}`,
            `Status:    ${result.status}`,
            ``,
            `${result.message}`,
            ``,
            `⚠️ This is ${process.env.MOCK_MODE === "true" ? "a MOCK SIP (no real investment)" : "a REAL SIP — money will be debited on schedule"}`,
          ].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. While 'Create' implies a write/mutation operation, it doesn't specify permissions required, whether the operation is idempotent, what happens on failure, or what the response contains. This is inadequate for a creation tool with zero annotation coverage.

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 a single, efficient sentence that states the core purpose and enumerates the key parameters without any fluff. Every word serves a functional purpose, making it optimally concise and well-structured.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a SIP is, what the response looks like, error conditions, or system behavior post-creation. The agent lacks critical context to use this tool effectively in real scenarios.

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%, so the schema already fully documents all parameters. The description lists the parameters but adds no additional semantic context beyond what's in the schema (e.g., format examples, business rules, or constraints). This meets the baseline for high schema coverage.

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 ('Create a new SIP') and specifies the key parameters (fund ISIN, amount, frequency, start date), making the purpose unambiguous. However, it doesn't explicitly differentiate this tool from sibling tools like 'invest_in_fund' or 'list_sips', which prevents a perfect score.

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 'invest_in_fund' or 'pause_sip'. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent to infer usage context from the tool name alone.

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