Skip to main content
Glama
darved2305

groww-mcp

by darved2305

remove_from_watchlist

Remove a stock symbol from your watchlist on Groww to declutter and focus on relevant investments.

Instructions

Remove a stock symbol from your watchlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol to remove
exchangeNoExchangeNSE

Implementation Reference

  • Tool registration and handler definition for remove_from_watchlist in the watchlist tools file.
    // ── remove_from_watchlist ─────────────────────────────────
    server.tool(
      "remove_from_watchlist",
      "Remove a stock symbol from your watchlist",
      {
        symbol: z.string().describe("Stock symbol to remove"),
        exchange: z.enum(["NSE", "BSE"]).default("NSE").describe("Exchange"),
      },
      async ({ symbol, exchange }) => {
        try {
          const sym = normalizeSymbol(symbol);
          const result = await growwClient.removeFromWatchlist(sym, exchange);
          return mcpText(`🗑️ ${sym}.${exchange} removed from watchlist`);
        } catch (err) {
          return mcpError(normalizeError(err));
        }
      }
    );
  • Actual API implementation for removing a stock symbol from the watchlist via GrowwClient.
    async removeFromWatchlist(symbol: string, exchange: string): Promise<{ status: string; message: string }> {
      if (isMockMode()) return { status: "success", message: `${symbol} removed from watchlist` };
      return this.request("DELETE", "/watchlist/remove", { symbol, exchange });
    }
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 the tool performs a removal operation, implying mutation, but lacks details on permissions required, whether the action is reversible, error handling (e.g., if the symbol isn't in the watchlist), or side effects. This is a significant gap for a mutation tool.

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, direct sentence with zero wasted words. It front-loads the core action and resource efficiently, making it easy to parse and understand at a glance.

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 the tool's mutation nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, reversibility, or response format, nor does it provide usage context relative to siblings. For a tool that modifies user data, this leaves critical gaps.

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 fully documents both parameters (symbol and exchange). The description mentions 'stock symbol' but doesn't add semantic context beyond what the schema provides, such as format examples or the relationship between symbol and exchange. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Remove') and resource ('stock symbol from your watchlist'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_watchlist' or 'add_to_watchlist' beyond the obvious verb difference, 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. It doesn't mention prerequisites (e.g., needing the symbol to already be in the watchlist), nor does it reference sibling tools like 'add_to_watchlist' or 'get_watchlist' for context, leaving usage entirely implicit.

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