Skip to main content
Glama
darved2305

groww-mcp

by darved2305
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

cancel_sip

Cancel a Systematic Investment Plan (SIP) permanently on Groww by providing the SIP ID to stop future investments.

Instructions

Cancel a SIP permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sip_idYesSIP ID to cancel

Implementation Reference

  • src/tools/sip.ts:120-136 (handler)
    The handler function for cancel_sip, which uses growwClient to cancel the SIP.
    async ({ sip_id }) => {
  try {
    const result = await growwClient.cancelSIP(sip_id);
    const text = [
      `🛑 SIP CANCELLED`,
      `${"─".repeat(40)}`,
      `SIP ID:  ${result.sipId}`,
      `Status:  ${result.status}`,
      `${result.message}`,
      ``,
      `⚠️ This action is permanent. You'll need to create a new SIP to resume investing.`,
    ].join("\n");
    return mcpText(text);
  } catch (err) {
    return mcpError(normalizeError(err));
  }
}
  • src/tools/sip.ts:114-119 (registration)
    Tool registration for cancel_sip, including input schema definition.
    server.tool(
  "cancel_sip",
  "Cancel a SIP permanently",
  {
    sip_id: z.string().describe("SIP ID to cancel"),
  },

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action is 'permanent', which implies an irreversible destructive operation, but doesn't disclose other behavioral traits like authentication requirements, rate limits, error conditions, or what happens to associated funds. For a destructive tool with zero annotation coverage, this is insufficient.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place.

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?

Given this is a destructive operation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'permanently' entails (e.g., funds returned, cancellation fee), expected response, or error handling. For a tool that permanently cancels financial transactions, more context is needed.

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 the single parameter 'sip_id' fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., format examples, validation rules). Baseline 3 is appropriate when the schema does all the work.

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 ('Cancel') and target resource ('a SIP'), making the purpose immediately understandable. It distinguishes from siblings like 'pause_sip' by specifying 'permanently', though it doesn't explicitly contrast with other cancellation tools like 'cancel_order'. The purpose is specific but could be more differentiated from similar tools.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., SIP must exist), exclusions (e.g., cannot cancel if already completed), or when to choose this over 'pause_sip' or 'cancel_order'. The description lacks any contextual usage information.

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