Skip to main content
Glama
PHUICMT

mcp-mt5

by PHUICMT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select_terminal

Switch the active MetaTrader terminal data folder for the current session. Provide an origin path, 32-character hash, or install directory to direct all subsequent tool calls to the selected layout.

Instructions

Switch the active terminal data folder for this session.

Provide one of: origin (install path stored in origin.txt), hash (32-char folder name), or install (auto-scan for the matching origin).

Subsequent tool calls will use the new layout until the server restarts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashNo32-character terminal data folder name under %APPDATA%\\MetaQuotes\\Terminal.
originNoInstall path stored in the terminal's origin.txt, e.g. C:\\Program Files\\MetaTrader 5.
editionNo"mt5" or "mt4".mt5
installNoInstall folder containing terminal64.exe; its data folder is found by scanning origin.txt files.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / properties / edition / description
      Added value: +"\"mt5\" or \"mt4\"."
    • addedInput schema / properties / hash / description
      Added value: +"32-character terminal data folder name under %APPDATA%\\\\MetaQuotes\\\\Terminal."
    • addedInput schema / properties / install / description
      Added value: +"Install folder containing terminal64.exe; its data folder is found by scanning origin.txt files."
    • addedInput schema / properties / origin / description
      Added value: +"Install path stored in the terminal's origin.txt, e.g. C:\\\\Program Files\\\\MetaTrader 5."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "select_terminalDictOutput",
+  "type": "object"
+}
  2. First observedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the lasting side effect ('Subsequent tool calls will use the new layout until the server restarts'), which is valuable because annotations only report false hints. It does not over-promise persistence or claim destructive behavior.

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 description is short, front-loaded with the core action, and every sentence contributes either a mode definition or a behavioral consequence. There is no redundant phrasing or filler.

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?

For a simple session-switching tool, the description covers the selection modes and the session-scoped lifecycle. It leaves minor ambiguity about what happens if no mode or multiple modes are supplied, but the schema and output schema cover the remaining details.

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%, so the schema already documents each parameter. The description adds the useful notion that these are mutually exclusive selection modes, but it does not mention the edition parameter and adds only modest semantic value beyond the schema.

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 first sentence states a specific action ('Switch'), resource ('active terminal data folder'), and scope ('for this session'). This clearly differentiates it from sibling tools like list_terminals or kill_terminal, and the name does not need to be restated.

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?

The description explicitly instructs the agent to provide one of origin, hash, or install and explains what each option means. It gives clear selection context for the parameter modes, though it does not explicitly compare this tool to sibling alternatives such as list_terminals for discovering folder hashes.

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

Deploy Server

Other Tools