Skip to main content
Glama
darved2305

groww-mcp

by darved2305

get_market_status

Check if the NSE and BSE stock exchanges are currently open for trading to determine when to execute orders or analyze market data.

Instructions

Check if NSE/BSE is currently open for trading

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for get_market_status, which fetches market status from the growwClient and formats the response.
    server.tool(
      "get_market_status",
      "Check if NSE/BSE is currently open for trading",
      {},
      async () => {
        try {
          const statuses = await growwClient.getMarketStatus();
    
          const lines = statuses.map((s) => {
            const icon = s.status === "OPEN" ? "🟢" : s.status === "PRE_OPEN" ? "🟡" : "🔴";
            return `${icon} ${s.exchange}: ${s.status} — ${s.message}`;
          });
    
          const text = [`🏛️ MARKET STATUS`, `${"─".repeat(40)}`, ...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 states the tool's function but lacks behavioral details such as rate limits, authentication requirements, response format, or error conditions. This is a significant gap for a 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 is front-loaded with the core purpose, making it easy to parse and understand immediately.

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 simplicity (0 parameters, no output schema) and lack of annotations, the description is adequate but minimal. It covers the basic purpose but lacks details on behavior, output, or error handling, which could be useful for an agent despite the low complexity.

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 no parameter documentation is needed. The description appropriately does not discuss parameters, aligning with the schema. Baseline is 4 for zero parameters, as it avoids unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Check') and resource ('if NSE/BSE is currently open for trading'), with precise scope (current trading status). It effectively distinguishes from siblings like get_ohlc_data or get_quote, which retrieve market data rather than operational status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (determining market hours for trading decisions) but does not explicitly state when to use it versus alternatives. No guidance on prerequisites or exclusions is provided, leaving usage context inferred rather than specified.

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