tradingcli

order_submit

Submit market, limit, stop, stop-limit, trailing, bracket, OCO, or OTO orders to execute trades directly from your account.

Instructions

Submit market, limit, stop, stop-limit, trailing, bracket, OCO, or OTO orders.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "symbol": "<symbol>",
      "side": "<side>"
    },
    "name": "order_submit"
  }
}

Input Schema

Name	Required	Default
`qty`	No
`side`	Yes
`agent`	No	mcp
`symbol`	Yes
`account`	Yes
`dry_run`	No
`notional`	No
`stop_loss`	No
`order_type`	No	market
`stop_price`	No
`limit_price`	No
`order_class`	No	simple
`take_profit`	No
`trail_price`	No
`time_in_force`	No	gtc
`trail_percent`	No
`extended_hours`	No
`client_order_id`	No
`idempotency_key`	No
`stop_loss_limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It fails to mention that this places real financial orders, that dry_run is available for simulation, or any idempotency/error behavior. This is a high-stakes tool, so the lack of caution is significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It efficiently states the tool's action and scope, though the extreme brevity leaves out critical usage details. For conciseness, it is well-structured.

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 (20 parameters, 0% schema coverage, no annotations), the description is far from complete. It lists order types but lacks any guidance on parameter selection, risk, or workflow. The output schema doesn't reduce the need for usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 20 parameters with zero descriptions in the schema itself, so the description must compensate. It merely lists order types without explaining how to configure them—e.g., which parameters are needed for a stop-limit vs. trailing, the difference between qty and notional, or the meaning of order_class and time_in_force. This adds no parameter-level value.

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 uses the specific verb 'Submit' and identifies the resource 'orders', explicitly enumerating eight order types (market, limit, stop, etc.). This clearly distinguishes it from sibling tools like preview_order, order_cancel, and order_replace, which serve different actions.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention preview_order for testing, order_cancel for cancellations, or any prerequisites like account permissions or safety checks. The only implicit hint is the word 'Submit'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server