Skip to main content
Glama

place_order

Places buy, sell, or close orders on an MT5 account and applies server safety limits. Use test mode to validate an order without sending a real trade.

Instructions

Bir MT5 hesabında emir gönderir: buy/sell (volume gerekli) veya close. Sunucu güvenlik limitlerini (volume tavanı, izinli semboller, üyelik/plan) uygular. test=true ise doğrulama yapılır ama GERÇEK EMİR gönderilmez.

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": {
      "accountId": "<accountId>",
      "action": "<action>",
      "symbol": "<symbol>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoİdempotensi anahtarı (aynı id tekrar gönderilirse yeniden işlenmez)
slNoStop-loss fiyatı (opsiyonel)
tpNoTake-profit fiyatı (opsiyonel)
testNotrue → sadece doğrula, gerçek emir gönderme
magicNoMT5 magic number (strateji ayırımı); close'ta verilirse yalnız o magic'li pozisyonlar kapanır
actionYesEmir tipi
symbolYesSembol, ör. EURUSD / XAUUSD
volumeNoLot (buy/sell için gerekli)
commentNoAçılan emrin MT5 yorumu (en fazla 31 karakter kullanılır)
accountIdYesHedef MT5 hesap id
closeOppositeNotrue → buy/sell öncesi aynı sembolün ters yöndeki pozisyonlarını kapat (reverse)
allowDuplicateNofalse → aynı sembolde aynı yönde (magic verildiyse aynı magic'li) açık pozisyon varsa yeni emir açma

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden: it usefully discloses that the server enforces security limits (volume cap, allowed symbols, membership/plan) and that test=true validates without sending a real order. It omits what a real order does irreversibly, error/failure behavior, and what the call returns.

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 compact sentences: action mode and volume requirement first, then limit enforcement, then the dry-run caveat. No filler, though it could front-load the dry-run mode more prominently for a mutation tool.

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

Completeness3/5

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

For a 12-parameter mutation tool with no annotations and no output schema, the description covers actions and safety limits but says nothing about the response shape or failure modes. It is adequate but leaves an agent guessing about outcomes.

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% across 12 parameters, so idempotency (id), sl/tp, magic filtering on close, closeOpposite, and allowDuplicate are already documented. The description only restates the volume requirement for buy/sell, adding little beyond the schema.

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 names a specific verb and resource: send an order on an MT5 account, with the two modes (buy/sell with required volume, or close). It does not name a sibling for contrast, but the write/placement intent is unmistakable against read-only siblings like get_positions.

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?

It gives implied routing between the actions (buy/sell needs volume; close closes) and explicitly frames test=true as the dry-run path. It never states when to use this instead of get_open_positions or get_trades, nor prerequisite conditions beyond the server-side limit note.

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