Skip to main content
Glama
darved2305

groww-mcp

by darved2305

get_watchlist

Retrieve your stock watchlist with current prices and daily changes to monitor market positions on Groww.

Instructions

List all watchlist symbols with LTP and day change

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for get_watchlist that fetches the watchlist data and formats it for output.
    async () => {
      try {
        const items = await growwClient.getWatchlist();
        if (items.length === 0) return mcpText("📭 Watchlist is empty. Add symbols to track them.");
    
        const lines = items.map((w) => {
          const emoji = pnlEmoji(w.change);
          return `${emoji} ${w.symbol.padEnd(12)} ${formatCurrencyExact(w.ltp).padStart(12)}  ${pnlSign(w.change)} (${formatPercent(w.changePercent)})  ${w.name}`;
        });
    
        const text = [
          `👁️ WATCHLIST (${items.length} symbols)`,
          `${"─".repeat(70)}`,
          ...lines,
          ``,
          `As of ${nowIST()}`,
        ].join("\n");
        return mcpText(text);
      } catch (err) {
        return mcpError(normalizeError(err));
      }
    }
  • Registration of the get_watchlist tool using server.tool.
    server.tool(
      "get_watchlist",
      "List all watchlist symbols with LTP and day change",
      {},
      async () => {
        try {
          const items = await growwClient.getWatchlist();
          if (items.length === 0) return mcpText("📭 Watchlist is empty. Add symbols to track them.");
    
          const lines = items.map((w) => {
            const emoji = pnlEmoji(w.change);
            return `${emoji} ${w.symbol.padEnd(12)} ${formatCurrencyExact(w.ltp).padStart(12)}  ${pnlSign(w.change)} (${formatPercent(w.changePercent)})  ${w.name}`;
          });
    
          const text = [
            `👁️ WATCHLIST (${items.length} symbols)`,
            `${"─".repeat(70)}`,
            ...lines,
            ``,
            `As of ${nowIST()}`,
          ].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?

No annotations are provided, so the description carries full burden. It implies a read-only operation ('List'), but doesn't disclose behavioral traits like authentication requirements, rate limits, pagination, error conditions, or whether it returns real-time or cached data. For a financial tool with no annotation coverage, this is a significant gap.

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 waste. It's front-loaded with the core purpose and includes essential details (LTP and day change) without unnecessary elaboration. Every word earns its place.

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?

Given the tool's complexity (simple read operation with no parameters) and lack of annotations/output schema, the description is minimally adequate. It states what data is returned but lacks context on format, limitations, or behavioral aspects. It's complete enough for basic use but leaves gaps for reliable agent invocation.

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 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters, as it doesn't introduce confusion or omissions.

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's purpose: 'List all watchlist symbols with LTP and day change.' It specifies the verb ('List'), resource ('watchlist symbols'), and key data fields ('LTP and day change'). However, it doesn't explicitly differentiate from sibling tools like 'get_quote' or 'get_top_movers,' 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 a watchlist set up), exclusions, or comparisons to siblings like 'get_quote' (for single symbols) or 'get_top_movers' (for market trends). This leaves the agent without context for tool selection.

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