Skip to main content
Glama
darved2305

groww-mcp

by darved2305

get_order_status

Check real-time status of a specific order by providing the order ID to track execution and completion details.

Instructions

Real-time status of a specific order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder ID to check

Implementation Reference

  • The handler for the "get_order_status" tool, which uses `growwClient` to fetch order details and formats the output.
    // ── get_order_status ──────────────────────────────────────
    server.tool(
      "get_order_status",
      "Real-time status of a specific order",
      {
        order_id: z.string().describe("Order ID to check"),
      },
      async ({ order_id }) => {
        try {
          const o = await growwClient.getOrderStatus(order_id);
    
          const statusEmoji: Record<string, string> = {
            EXECUTED: "✅", PENDING: "⏳", CANCELLED: "❌", REJECTED: "🚫", PARTIAL: "🔶",
          };
          const emoji = statusEmoji[o.status] || "❓";
    
          const text = [
            `${emoji} ORDER STATUS`,
            `${"─".repeat(40)}`,
            `Order ID:  ${o.orderId}`,
            `Symbol:    ${o.symbol}.${o.exchange}`,
            `Action:    ${o.orderType} / ${o.priceType} / ${o.productType}`,
            `Quantity:  ${o.quantity}${o.filledQuantity > 0 ? ` (filled: ${o.filledQuantity})` : ""}`,
            o.price > 0 ? `Price:     ${formatCurrencyExact(o.price)}` : `Price:     MARKET`,
            o.avgFilledPrice > 0 ? `Avg Fill:  ${formatCurrencyExact(o.avgFilledPrice)}` : "",
            `Status:    ${o.status}`,
            o.remarks ? `Remarks:   ${o.remarks}` : "",
            ``,
            `As of ${nowIST()}`,
          ].filter(Boolean).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?

With no annotations provided, the description carries full burden but only states 'real-time status' without clarifying what that entails (e.g., response format, latency, authentication needs, or rate limits). It misses critical behavioral details for a status-checking tool.

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 appropriately sized and front-loaded, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'status' includes (e.g., pending, executed, failed) or return values, leaving gaps for an AI agent to understand the tool's full context.

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?

The schema description coverage is 100%, with the parameter 'order_id' well-documented in the schema. The description adds no additional meaning beyond implying a specific order context, so it meets the baseline for high schema coverage without compensating value.

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 'Real-time status of a specific order' clearly states the verb ('status') and resource ('order'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_order_history' or 'modify_order', 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 like 'get_order_history' for historical data or 'modify_order' for updates. It lacks any context about prerequisites or exclusions, leaving usage decisions ambiguous.

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