fxapis — MetaTrader 5

Place a limit or stop order

place_pending_order

DestructiveIdempotent

Places a limit or stop order on the user's real broker account (or demo) that waits at the broker; success means working, not filled. Confirm it with the user first. Example: {"account_id": "", "symbol": "EURUSD", "side": "buy", "kind": "limit", "volume": "0.10", "price": "1.08000", "idempotency_key": ""}

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	limit, stop or stop_limit.
`side`	Yes	buy or sell.
`price`	Yes	The price the order waits at. An absolute price (e.g. "1.08450"), not a distance in pips or points.
`symbol`	Yes	The symbol exactly as this broker names it, e.g. "EURUSD" — some brokers add a suffix such as "EURUSD.r".
`volume`	Yes	Order size. In lots, preferably as a string: "0.01" is a micro lot, "1.00" a standard lot.
`comment`	No	Optional note stored on the order. MT5 keeps the first 17 characters after our reference.
`stop_loss`	No	Optional stop loss. An absolute price (e.g. "1.08450"), not a distance in pips or points.
`account_id`	Yes	The fxapis account id (a UUID) from list_accounts — not the MT5 login number.
`expires_at`	No	When the broker should drop it. Omit for good-till-cancelled.
`take_profit`	No	Optional take profit. An absolute price (e.g. "1.08450"), not a distance in pips or points.
`client_order_id`	No	Optional reference of your own, echoed back on the order.
`idempotency_key`	Yes	A unique string you generate for THIS action, e.g. a fresh UUID. If a call fails or times out and you retry the same action, send the SAME key: fxapis then returns the first result instead of acting twice. Use a new key only for a genuinely new action.
`stop_limit_price`	No	Required for stop_limit: the limit placed once the stop triggers. An absolute price (e.g. "1.08450"), not a distance in pips or points.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`order`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructive/openWorld/idempotent, but the description adds value they don't carry: that this touches a real (or demo) broker account and that a successful response means a working order, not a filled one. It does not restate the idempotency behavior, which the idempotency_key parameter already documents thoroughly.

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?

Three tight sentences with the most consequential facts front-loaded (real account, working-not-filled), followed by a compact example. The example earns its space by showing the call shape, though it is the one non-sentence element.

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

Completeness4/5

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

With an output schema, full param coverage, and annotations covering the safety profile, the description only needed to supply the semantic gaps, which it does: real-vs-demo account, working-not-filled outcome, and the user-confirmation requirement. Coverage is strong, with only optional-field edge cases left to the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond that by giving a complete worked example payload, showing the required-field shape and format for a successful call. It does not add semantics for the optional fields, but the schema covers those.

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?

States a specific verb and resource ('places a limit or stop order') plus the critical scope distinction that it 'waits at the broker' and 'success means working, not filled'. This differentiates it from place_market_order and place_multi_account_order without needing the schemas.

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?

Gives an explicit workflow prerequisite ('Confirm it with the user first') and implies the pending-vs-immediate distinction against the market-order siblings. It stops short of naming an alternative tool or stating when-not to use it, so it is clear context without explicit routing.

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

All fxapis — MetaTrader 5 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?