Skip to main content
Glama
darved2305

groww-mcp

by darved2305

search_stocks

Search for stocks and mutual funds by name or ticker symbol to find investment opportunities on Groww.

Instructions

Fuzzy search stocks and MFs by name or ticker

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query — stock name, ticker, or keyword

Implementation Reference

  • The "search_stocks" tool is registered and its handler logic is implemented within the server.tool block in src/tools/market.ts. It uses growwClient.searchStocks to perform the search.
    // ── search_stocks ─────────────────────────────────────────
    server.tool(
      "search_stocks",
      "Fuzzy search stocks and MFs by name or ticker",
      {
        query: z.string().describe("Search query — stock name, ticker, or keyword"),
      },
      async ({ query }) => {
        try {
          const results = await growwClient.searchStocks(query);
          if (results.length === 0) return mcpText(`🔍 No results found for "${query}"`);
    
          const lines = results.map((r, i) =>
            `${i + 1}. ${r.symbol} — ${r.name} [${r.exchange}] (${r.type}) ISIN: ${r.isin}`
          );
    
          const text = [`🔍 SEARCH: "${query}" — ${results.length} results`, `${"─".repeat(40)}`, ...lines].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 mentions 'fuzzy search' but doesn't disclose behavioral traits like result format, pagination, rate limits, or authentication needs. This is inadequate for a search tool with zero annotation coverage.

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 and appropriately sized for a simple search tool.

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 no annotations and no output schema, the description is incomplete. It lacks details on return values, error handling, or usage context, which are critical for a search tool with one parameter but undefined behavior.

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 documents the 'query' parameter. The description adds marginal value by clarifying it accepts 'name, ticker, or keyword', but doesn't provide syntax or format details beyond what the schema implies.

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 ('fuzzy search') and resources ('stocks and MFs'), specifying it works by 'name or ticker'. It distinguishes from sibling 'search_funds' by covering both stocks and mutual funds, though the distinction could be more explicit.

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 like 'search_funds' or 'get_quote'. The description implies it's for searching, but doesn't specify contexts, prerequisites, or exclusions.

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