Skip to main content
Glama
darved2305

groww-mcp

by darved2305

get_top_movers

Retrieve the top 5 gaining and losing stocks for the current trading day to monitor market performance.

Instructions

Top 5 gainers and losers for the day

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_top_movers' MCP tool, which fetches market movers via the growwClient and formats them into a text report.
    // ── get_top_movers ────────────────────────────────────────
    server.tool(
      "get_top_movers",
      "Top 5 gainers and losers for the day",
      {},
      async () => {
        try {
          const { gainers, losers } = await growwClient.getTopMovers();
    
          const gLines = gainers.map((g, i) =>
            `  ${i + 1}. ${g.symbol.padEnd(12)} ${formatCurrencyExact(g.ltp).padStart(12)}  ${formatPercent(g.changePercent)}`
          );
          const lLines = losers.map((l, i) =>
            `  ${i + 1}. ${l.symbol.padEnd(12)} ${formatCurrencyExact(l.ltp).padStart(12)}  ${formatPercent(l.changePercent)}`
          );
    
          const text = [
            `🏆 TOP MOVERS — ${new Date().toLocaleDateString("en-IN", { timeZone: "Asia/Kolkata" })}`,
            `${"─".repeat(50)}`,
            `📈 GAINERS`,
            ...gLines,
            ``,
            `📉 LOSERS`,
            ...lLines,
            ``,
            `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 mentions 'for the day' which implies time-bound data, but doesn't disclose critical behaviors like whether it requires authentication, rate limits, data freshness, or error conditions. For a financial data tool with zero 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 appropriately sized for a simple tool with no parameters.

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 complexity (simple read operation) but lack of annotations and output schema, the description is incomplete. It doesn't explain what data is returned (e.g., format, fields), error handling, or dependencies like market hours. For a tool in a financial context with siblings requiring auth, this should provide more context.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for zero parameters, as no compensation is needed.

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: retrieving the top 5 gainers and losers for the day. It specifies the verb ('get' implied by name) and resource (market movers), though it doesn't explicitly differentiate from siblings like get_quote or search_stocks. The description is specific but lacks sibling comparison.

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, context (e.g., market hours), or compare to siblings like get_market_status or search_stocks for similar data. Usage is implied by the name and description but not explicitly stated.

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