mcp-mt5

Overview Schema Source Related Servers Discussions Admin

top_passes

Read-onlyIdempotent

Retrieve top optimization passes from MetaTrader backtest results, ranked by criteria like profit, and filter by symbol, period, or expert.

Instructions

DEPRECATED (removed in 0.6.0): use read_optimization(criterion=..., top_n=...).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`n`	No	How many passes to return.
`expert`	No	Expert name to select the cache.
`period`	No	Timeframe to select the cache.
`symbol`	No	Symbol to select the cache.
`opt_path`	No	Absolute path to a .opt cache.
`criterion`	No	Pass field to rank by.	profit
`descending`	No	true = highest first.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.5.0Sep 11, 2026

addedInput schema / properties / criterion / description
```
Added value: +"Pass field to rank by."
```
addedInput schema / properties / descending / description
```
Added value: +"true = highest first."
```

addedInput schema / properties / expert

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Expert name to select the cache.",
+  "title": "Expert"
+}

addedInput schema / properties / n / description
```
Added value: +"How many passes to return."
```
addedInput schema / properties / opt_path / description
```
Added value: +"Absolute path to a .opt cache."
```

addedInput schema / properties / period

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Timeframe to select the cache.",
+  "title": "Period"
+}

addedInput schema / properties / symbol

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Symbol to select the cache.",
+  "title": "Symbol"
+}

changedOutput schema / (root)

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

First observedv0.4.1Jun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds the critical behavioral fact of deprecation and removal in 0.6.0, which annotations do not cover. The read-only and idempotent hints are already provided by annotations, so the description adds valuable context about the tool's status.

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?

A single, front-loaded sentence that immediately flags deprecation and gives the replacement call. Zero waste and highly scannable.

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 deprecated tool, the description fully serves its purpose by directing the agent away. The output schema and annotations cover the rest, and no additional detail about return values or behavior is necessary.

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 descriptions cover all 7 parameters with clear meanings. The tool description adds no parameter-specific guidance, but the deprecation notice implicitly tells the agent not to worry about parameters. Baseline 3 applies given 100% schema coverage.

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 clearly states the tool is deprecated and directs the agent to a replacement, which is a specific purpose for a deprecated tool. It distinguishes itself from siblings by naming the successor, though it does not describe the original functionality beyond the name and parameters.

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?

Explicitly instructs the agent to use read_optimization(criterion=..., top_n=...) instead, leaving no ambiguity about when or whether to use this tool. This is ideal guidance.

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