mcp-mt5

Overview Schema Source Related Servers Discussions Admin

kill_terminal

Destructive

Force-kill terminal processes launched by this server to stop stuck backtests or smoke tests, leaving live trading terminals untouched. Use all_instances=True to kill all terminal instances.

Instructions

Force-kill terminal processes launched by this server (run_backtest / smoke_test).

By default only PIDs this server started are killed, so a live-trading terminal on the same machine is never touched. Pass all_instances=True to taskkill every terminal64.exe/terminal.exe of the configured edition (destructive).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`all_instances`	No	false = only terminals launched by this server; true = taskkill every terminal of this edition (may hit a live-trading terminal).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.0Sep 11, 2026

addedInput schema / properties / all_instances

Added value: +{
+  "default": false,
+  "description": "false = only terminals launched by this server; true = taskkill every terminal of this edition (may hit a live-trading terminal).",
+  "title": "All Instances",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "kill_terminalDictOutput",
+  "type": "object"
+}

First observedv0.4.1Jun 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds meaningful behavioral context: the default scoping to server-started PIDs, the specific file names (terminal64.exe/terminal.exe), and the warning about live-trading terminals. This goes beyond the annotation's binary flag and helps the agent understand the exact blast radius.

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 two concise sentences, front-loading the default behavior and then the destructive alternative. Every clause carries meaning: it explains the default scope, the safety guarantee, and the explicit destructive flag. No redundancy or filler.

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 tool with a single optional parameter and a clear output schema, the description fully covers the behavior, the parameter semantics, and the safety profile. It tells the agent exactly when to use the default and when to escalate, and it addresses the risk of collateral damage. Nothing critical is missing for correct invocation.

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?

The schema already covers all_instances with a 100% description coverage, giving the baseline of 3. The description adds a small but useful detail: it specifies 'terminal64.exe/terminal.exe' for the all_instances case, which clarifies the exact processes affected. This is a slight enhancement over the schema's wording, justifying a 4.

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 a specific verb ('Force-kill') and a clear resource ('terminal processes launched by this server'), and explicitly ties it to run_backtest / smoke_test. It also distinguishes this tool from the sibling select_terminal and list_terminals by stating what it does not touch (live-trading terminals).

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

Usage Guidelines5/5

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

The description gives explicit when-to-use context: by default it only kills server-launched PIDs, and it warns that passing all_instances=True is destructive and may affect a live-trading terminal. It effectively says when not to use the destructive option and clarifies the safe default, leaving no ambiguity about which invocation to choose.

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