Skip to main content
Glama
darved2305

groww-mcp

by darved2305

place_order

Execute BUY or SELL orders for stocks with MARKET/LIMIT pricing and CNC/MIS/NRML product types on Groww trading platform.

Instructions

Place BUY/SELL order — supports MARKET/LIMIT, CNC/MIS/NRML product types

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol, e.g. RELIANCE
exchangeNoExchangeNSE
order_typeYesBUY or SELL
product_typeNoCNC (delivery), MIS (intraday), NRML (F&O)CNC
price_typeNoMARKET or LIMIT orderMARKET
quantityYesNumber of shares
priceNoLimit price (required for LIMIT orders)
trigger_priceNoStop-loss trigger price

Implementation Reference

  • The "place_order" tool is defined using server.tool, validating inputs with Zod, and calling the growwClient.placeOrder method.
    server.tool(
      "place_order",
      "Place BUY/SELL order — supports MARKET/LIMIT, CNC/MIS/NRML product types",
      {
        symbol: z.string().describe("Stock symbol, e.g. RELIANCE"),
        exchange: z.enum(["NSE", "BSE"]).default("NSE").describe("Exchange"),
        order_type: z.enum(["BUY", "SELL"]).describe("BUY or SELL"),
        product_type: z.enum(["CNC", "MIS", "NRML"]).default("CNC").describe("CNC (delivery), MIS (intraday), NRML (F&O)"),
        price_type: z.enum(["MARKET", "LIMIT"]).default("MARKET").describe("MARKET or LIMIT order"),
        quantity: z.number().int().positive().describe("Number of shares"),
        price: z.number().positive().optional().describe("Limit price (required for LIMIT orders)"),
        trigger_price: z.number().positive().optional().describe("Stop-loss trigger price"),
      },
      async ({ symbol, exchange, order_type, product_type, price_type, quantity, price, trigger_price }) => {
        try {
          if (price_type === "LIMIT" && !price) {
            return mcpError("Limit price is required for LIMIT orders");
          }
    
          const sym = normalizeSymbol(symbol);
          const result = await growwClient.placeOrder({
            symbol: sym,
            exchange,
            orderType: order_type,
            productType: product_type,
            priceType: price_type,
            quantity,
            price: price ?? 0,
            triggerPrice: trigger_price ?? 0,
          });
    
          const emoji = order_type === "BUY" ? "🟢" : "🔴";
          const text = [
            `${emoji} ORDER PLACED`,
            `${"─".repeat(40)}`,
            `Order ID:  ${result.orderId}`,
            `Status:    ${result.status}`,
            `Action:    ${order_type} ${sym}.${exchange}`,
            `Type:      ${price_type} / ${product_type}`,
            `Quantity:  ${quantity}`,
            price_type === "LIMIT" ? `Price:     ${formatCurrencyExact(price!)}` : `Price:     MARKET`,
            trigger_price ? `Trigger:   ${formatCurrencyExact(trigger_price)}` : "",
            ``,
            `${result.message}`,
            ``,
            `⚠️ This is ${process.env.MOCK_MODE === "true" ? "a MOCK order (no real trade)" : "a REAL order with real money"}`,
          ].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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions order types and product types, it fails to describe critical behaviors such as authentication requirements, rate limits, execution guarantees, error handling, or financial implications (e.g., funds deduction, margin requirements). For a high-stakes financial tool with no annotations, 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, dense sentence with zero waste—it efficiently communicates the tool's core functionality and key supported features without redundancy. Every word earns its place, making it highly front-loaded and easy to parse.

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 complexity of a financial order placement tool with no annotations and no output schema, the description is insufficient. It lacks details on return values, error conditions, side effects (e.g., fund transfers, position changes), and operational constraints. For a tool with 8 parameters and high stakes, more comprehensive guidance is needed.

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 all parameters thoroughly. The description adds minimal value beyond the schema by highlighting key parameter categories (BUY/SELL, MARKET/LIMIT, product types) but does not provide additional semantic context like interdependencies (e.g., price required for LIMIT orders, which is already in the schema) or usage examples.

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 action ('Place BUY/SELL order') and specifies the resource (orders) with key supported features (MARKET/LIMIT price types, CNC/MIS/NRML product types). It distinguishes this tool from siblings like cancel_order, modify_order, or get_order_status by focusing on order creation rather than modification, cancellation, or querying.

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 for placing orders, but does not explicitly state when to use this tool versus alternatives like modify_order or cancel_order. It mentions supported features but lacks guidance on prerequisites (e.g., account funding, market hours) or exclusions (e.g., when not to use certain product types).

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