firstrade-mcp-server

Overview Schema Source Related Servers Discussions Admin

place_option_order

Place a real option order after previewing it. Uses the confirm token from preview_option_order to submit the exact trade to Firstrade.

Instructions

Place a real option order (dry_run=False). Requires FT_ALLOW_LIVE_ORDERS=true in .env AND a confirm_token from preview_option_order called with these exact same arguments — the server rejects the order otherwise, it does not just rely on the caller having "meant to" preview first.

Args: option_symbol: OCC format symbol (e.g. 'AAPL250620C00150000'). order_type: buy_to_open | sell_to_close | sell_to_open | buy_to_close ('buy' = buy_to_open, 'sell' = sell_to_open; to exit a long option you MUST use sell_to_close, otherwise Firstrade treats it as opening a short and rejects with ref 1103). contracts: Number of contracts. confirm_token: Token returned by preview_option_order for this exact order. price_type: limit | market | stop | stop_limit duration: day | day_ext | gt90 price: Limit price per contract (required for limit orders). stop_price: Stop trigger price (required for stop/stop_limit orders).

Returns JSON with order confirmation. This sends a real order to Firstrade.

Input Schema

TableJSON Schema

Name	Required	Default
`price`	No
`duration`	No	day
`contracts`	Yes
`order_type`	Yes
`price_type`	No	limit
`stop_price`	No
`confirm_token`	Yes
`option_symbol`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

There are no annotations, so the description carries the full burden. It discloses the real-money side effect ('This sends a real order to Firstrade'), the FT_ALLOW_LIVE_ORDERS environment requirement, the mandatory token validation, and the specific rejection risk for sell_to_close semantics.

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 critical 'real order' and prerequisite information is front-loaded, and the argument list is dense but organized. Every sentence contributes operational information, with no filler or repeated schema content.

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

Completeness5/5

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

For a high-risk live-order tool with 8 parameters, no annotations, and an output schema, the description gives the caller everything needed to invoke it correctly: prerequisites, token workflow, order-type edge cases, and price requirements.

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

Parameters5/5

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

Schema coverage is 0%, and the description compensates fully by documenting all 8 parameters, including OCC symbol format, order_type meanings with a must-use caveat, confirm_token provenance, price_type values, duration values, and required price/stop_price conditions.

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 opens with 'Place a real option order (dry_run=False)', stating a specific verb, resource, and mode. It clearly distinguishes itself from the preview/simulation siblings by emphasizing that this is a live order.

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

Usage Guidelines4/5

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

It gives an explicit required workflow: obtain confirm_token from preview_option_order with the exact same arguments, and warns that the server rejects otherwise. It does not explicitly name the alternative tool for dry-runs or spread orders, but the real-vs-preview distinction is strongly implied.

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

Deploy Server