Skip to main content
Glama
darved2305

groww-mcp

by darved2305

list_sips

View all active Systematic Investment Plans (SIPs) with fund names, investment amounts, and upcoming payment dates for managing mutual fund investments on Groww.

Instructions

All active SIPs with fund name, amount, next date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'list_sips' tool, which fetches SIPs from the client and formats the response.
    async () => {
      try {
        const sips = await growwClient.listSIPs();
        if (sips.length === 0) return mcpText("📭 No SIPs found. Create one to start systematic investing.");
    
        const lines = sips.map((s) => {
          const statusIcon = s.status === "ACTIVE" ? "🟢" : s.status === "PAUSED" ? "🟡" : "🔴";
          const pnl = s.currentValue - s.totalInvested;
          const pnlPct = s.totalInvested > 0 ? (pnl / s.totalInvested) * 100 : 0;
    
          return [
            `${statusIcon} ${s.fundName}`,
            `   SIP ID: ${s.sipId}  |  Status: ${s.status}`,
            `   Amount: ${formatCurrencyExact(s.amount)} / ${s.frequency}`,
            `   Instalments: ${s.instalments}  |  Next: ${s.nextDate}`,
            `   Invested: ${formatCurrency(s.totalInvested)}  |  Current: ${formatCurrency(s.currentValue)}`,
            `   Returns: ${pnlSign(pnl)} (${formatPercent(pnlPct)})`,
          ].join("\n");
        });
    
        const header = `📅 YOUR SIPs (${sips.length})\n${"─".repeat(55)}`;
        return mcpText([header, ...lines, `\nAs of ${nowIST()}`].join("\n\n"));
      } catch (err) {
        return mcpError(normalizeError(err));
      }
    }
  • src/tools/sip.ts:16-46 (registration)
    Registration of the 'list_sips' tool using server.tool.
    server.tool(
      "list_sips",
      "All active SIPs with fund name, amount, next date",
      {},
      async () => {
        try {
          const sips = await growwClient.listSIPs();
          if (sips.length === 0) return mcpText("📭 No SIPs found. Create one to start systematic investing.");
    
          const lines = sips.map((s) => {
            const statusIcon = s.status === "ACTIVE" ? "🟢" : s.status === "PAUSED" ? "🟡" : "🔴";
            const pnl = s.currentValue - s.totalInvested;
            const pnlPct = s.totalInvested > 0 ? (pnl / s.totalInvested) * 100 : 0;
    
            return [
              `${statusIcon} ${s.fundName}`,
              `   SIP ID: ${s.sipId}  |  Status: ${s.status}`,
              `   Amount: ${formatCurrencyExact(s.amount)} / ${s.frequency}`,
              `   Instalments: ${s.instalments}  |  Next: ${s.nextDate}`,
              `   Invested: ${formatCurrency(s.totalInvested)}  |  Current: ${formatCurrency(s.currentValue)}`,
              `   Returns: ${pnlSign(pnl)} (${formatPercent(pnlPct)})`,
            ].join("\n");
          });
    
          const header = `📅 YOUR SIPs (${sips.length})\n${"─".repeat(55)}`;
          return mcpText([header, ...lines, `\nAs of ${nowIST()}`].join("\n\n"));
        } 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 the full burden of behavioral disclosure. It states what data is returned but doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, pagination, or error conditions. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 - a single phrase that efficiently communicates the core functionality and return data. Every word earns its place with no redundancy or unnecessary elaboration. It's front-loaded with the essential information.

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?

For a simple read operation with no parameters and no output schema, the description adequately covers what the tool returns. However, without annotations or output schema, it should ideally mention that this is a read-only operation and whether authentication is required. The description is minimally complete but could be more comprehensive.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't discuss parameters, maintaining focus on what the tool returns rather than what it accepts. This meets the baseline for zero-parameter tools.

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 tool lists active SIPs and specifies the data fields returned (fund name, amount, next date). It distinguishes from siblings like 'get_holdings' or 'get_portfolio_summary' by focusing specifically on SIPs. However, it doesn't explicitly mention that it's a read-only operation or differentiate from 'create_sip' or 'pause_sip' beyond scope.

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, whether it requires authentication, or how it differs from other portfolio-related tools like 'get_holdings' or 'get_portfolio_summary'. The user must infer usage from the tool name and description 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