Skip to main content
Glama
turtlehq-tech

turtlestack-lite

Official

create_order

Place trading orders on multiple brokers (Kite, Groww, Dhan, AngelOne) with support for all order types, varieties, and advanced features like stop-loss and AMO.

Instructions

Create a new trading order with full support for all Kite order types and varieties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amoNoPlace as After Market Order
tagNoOrder tag for tracking
priceNoPrice per share (required for LIMIT/SL orders)
brokerNoSpecific broker (optional, uses active if not specified)
productYesProduct type
segmentNoMarket segment (required for Groww)
varietyNoOrder variety (optional, auto-determined)
exchangeYesExchange
quantityYesNumber of shares
stoplossNoStop loss price (required for CO/BO orders)
validityNoOrder validity
squareoffNoSquare off price (required for BO orders)
order_typeYesOrder type
symboltokenNoSymbol token (required for AngelOne, unique identifier for instrument)
trigger_priceNoTrigger price (required for SL/SL-M orders)
trading_symbolYesTrading symbol (e.g., RELIANCE-EQ, INFY-EQ)
transaction_typeYesTransaction type
trailing_stoplossNoTrailing stop loss (optional for CO orders)
disclosed_quantityNoDisclosed quantity for iceberg orders
order_reference_idNoCustom order reference ID (8-20 alphanumeric chars, max 2 hyphens, auto-generated if not provided)
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full behavioral disclosure burden, but it only gives a high-level summary. It doesn't mention that variety is auto-determined, that broker is optional, or any error/return behavior. This is a significant omission for a complex order placement 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, well-structured sentence that front-loads the core purpose. It contains no filler or redundant information, earning full marks for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 20 parameters, no annotations, and no output schema, the description is severely incomplete. It fails to explain return values, prerequisites (like auth), conditional parameter requirements, or how this differs from sibling order tools. This leaves the agent without enough context to use it correctly.

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 coverage is 100% with detailed parameter descriptions, so the schema already provides semantics. The description adds no additional parameter meaning beyond what is already in the schema. Thus, the baseline score of 3 applies.

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 creates a trading order, using the verb 'Create' and specifying the resource ('trading order'). It also indicates broad support for 'all Kite order types and varieties', which conveys scope. However, it does not explicitly distinguish itself from specialized sibling tools like place_amo or place_bracket_order, leaving some potential for confusion.

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 explicit guidance on when to use this tool versus alternatives. Given the many specialized order placement siblings (place_amo, place_cover_order, etc.), the absence of usage context or exclusions is a notable gap. The claim 'full support' implies generality but doesn't clarify when a specialized tool would be preferred.

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/turtlehq-tech/turtlestack-lite'

If you have feedback or need assistance with the MCP directory API, please join our Discord server