Skip to main content
Glama

open_account

Creates a new MetaTrader 5 account with demo or live type, manual or auto login, and optional instance startup; auto login requires login, password, and server details.

Instructions

Yeni bir MT5 hesabı oluşturur (varsayılan: manuel login, demo) ve isteğe bağlı olarak instance başlatır. Auto login için login+password+mt5Server gerekir. region opsiyonel (en yakın sunucu seçimi).

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": {
      "brokerName": "<brokerName>"
    },
    "name": "open_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoDostça ad (ör. 'Test Hesabı')
loginNoMT5 hesap no (auto login için gerekli)
regionNoHedef bölge (opsiyonel)
passwordNoMT5 şifresi (auto login için gerekli; şifreli saklanır)
loginModeNoauto=otomatik login, manual=VNC'den kullanıcı girer (varsayılan)
mt5ServerNoMT5 server adı (auto login için gerekli)
brokerNameYesBroker adı
accountTypeNoHesap tipi (varsayılan demo)
startInstanceNoHesap açılınca instance da başlat (varsayılan true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that an instance may also be started as a side effect and that credentials are only needed for auto mode, but says nothing about permissions, failure behavior, or what a live account implies.

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 short sentences, front-loaded with the action and defaults, then the mode prerequisite, then the optional region hint. Nothing is padded, though the parenthetical style is slightly dense.

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 9-parameter mutation tool with no annotations and no output schema, the description covers defaults, mode prerequisites, and the instance side effect. It still leaves open what is returned and how live accounts or failures are handled.

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 already 100%, so the baseline is 3, but the description adds real meaning: it names the three parameters required together for auto login and explains that region drives nearest-server selection, which the schema only labels as optional.

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 states a specific verb and resource: creates a new MT5 account, with the two default modes (manual login, demo) named up front. It does not explicitly contrast with siblings such as list_accounts, but the create action is unambiguous.

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 clear conditional context: manual/demo are the defaults, and auto login requires login+password+mt5Server. It stops short of naming alternatives or when not to use it, so it lands below the top band.

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