Skip to main content
Glama
darved2305

groww-mcp

by darved2305

add_to_watchlist

Add stock symbols to your watchlist for tracking market data and managing equity holdings on the Groww platform.

Instructions

Add a stock symbol to your watchlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol to add, e.g. RELIANCE
exchangeNoExchangeNSE

Implementation Reference

  • The `add_to_watchlist` tool definition, input schema, and handler logic.
    server.tool(
      "add_to_watchlist",
      "Add a stock symbol to your watchlist",
      {
        symbol: z.string().describe("Stock symbol to add, e.g. RELIANCE"),
        exchange: z.enum(["NSE", "BSE"]).default("NSE").describe("Exchange"),
      },
      async ({ symbol, exchange }) => {
        try {
          const sym = normalizeSymbol(symbol);
          const result = await growwClient.addToWatchlist(sym, exchange);
          return mcpText(`✅ ${sym}.${exchange} added to watchlist`);
        } catch (err) {
          return mcpError(normalizeError(err));
        }
      }
    );
  • The `addToWatchlist` API client method that executes the actual HTTP request.
    async addToWatchlist(symbol: string, exchange: string): Promise<{ status: string; message: string }> {
      if (isMockMode()) return { status: "success", message: `${symbol} added to watchlist` };
      return this.request("POST", "/watchlist/add", { symbol, exchange });
    }
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 the action but doesn't reveal whether this requires authentication, has rate limits, affects existing watchlist entries, or what happens on success/failure. For a mutation 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 perfectly front-loaded with the core action and resource, making it immediately scannable and understandable.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address authentication requirements, error conditions, response format, or how it interacts with the watchlist system. Given the complexity of financial operations, 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%, so the schema already fully documents both parameters. The description doesn't add any parameter semantics beyond what's in the schema (e.g., format examples, constraints, or relationships between parameters). Baseline 3 is appropriate when 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 ('Add') and resource ('stock symbol to your watchlist'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling tool 'remove_from_watchlist' beyond the obvious verb difference, nor does it specify if this is for creating new watchlists or adding to existing ones.

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., authentication, existing watchlist), when not to use it, or how it relates to sibling tools like 'get_watchlist' or 'remove_from_watchlist'.

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