mcp-mt5

Overview Schema Source Related Servers Discussions Admin

parse_optimization

Read-onlyIdempotent

Parses MetaTrader 5 .opt cache files to extract optimization results and pass samples. Deprecated; use read_optimization instead.

Instructions

DEPRECATED (removed in 0.6.0): use read_optimization(...).

Input Schema

TableJSON Schema

Name	Required	Description
`path`	No	Absolute path to a .opt cache.
`expert`	No	Expert name to select the cache.
`period`	No	Timeframe to select the cache.
`sample`	No	Passes to include in passes_sample.
`symbol`	No	Symbol to select the cache.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.0Sep 11, 2026

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 / 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 / sample

Added value: +{
+  "default": 50,
+  "description": "Passes to include in passes_sample.",
+  "title": "Sample",
+  "type": "integer"
+}

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": "parse_optimizationDictOutput",
+  "type": "object"
+}

First observedv0.4.1Jun 11, 2026

TDQS

D1.6/5.0

Behavior2/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already declare the tool as a safe, non-destructive read. The description adds only the deprecation status heavily implying it is non-functional. It does not disclose any behavioral traits beyond 'removed', which is critical but still leaves ambiguity about what happens when called (likely error). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, extremely concise, but it is under-specified. It front-loads the deprecation warning and the alternative, which is useful, but it omission of any purpose or usage details makes it inadequate despite brevity.

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

Completeness1/5

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

Given that the tool is deprecated and removed, the description should clearly state that it is non-functional and must not be used, and point to the alternative. It does that, but it lacks any information about what the tool actually did (parse optimization data) which is necessary for an agent to understand the alternative's relevance. The output schema exists but the description doesn't need to explain return values; still, the overall context for a deprecated tool is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema documents all five parameters. The description provides no additional semantic meaning for parameters; it only names an alternative function. The parameter descriptions in schema are sufficient but generic (e.g., 'path', 'expert'), and the description does not compensate for any nuance, leaving a gap for a deprecated tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is 'DEPRECATED (removed in 0.6.0): use read_optimization(...).' It does not state what the tool does, only that it is deprecated and points to an alternative. The name 'parse_optimization' suggests parsing optimization data, but the description is a tautology of the deprecation status, not the purpose.

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

Usage Guidelines1/5

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

The description explicitly tells the agent to use read_optimization instead, which is a clear when-not-to-use directive. However, it provides no guidance on when the tool itself might be used (which is never, since it's removed), and no context about the alternative's usage. Thus, it is misleading for actual invocation.

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