mcp-mt5

Overview Schema Source Related Servers Discussions Admin

list_experts

Read-onlyIdempotent

List compiled Expert Advisors from the MT5/MT4 Experts directory, filtering by glob pattern and including subfolders when needed.

Instructions

List compiled EAs in Experts/ (defaults to *.ex5 for MT5, *.ex4 for MT4).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pattern`	No	Glob pattern; defaults to .ex5 on MT5 and .ex4 on MT4.
`recurse`	No	Include subfolders of Experts/.

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 / pattern / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / pattern / default
```
Previous value: -"*.ex5"New value: +null
```

addedInput schema / properties / pattern / description

Added value: +"Glob pattern; defaults to *.ex5 on MT5 and *.ex4 on MT4."

removedInput schema / properties / pattern / type
```
Removed value: -"string"
```
addedInput schema / properties / recurse / description
```
Added value: +"Include subfolders of Experts/."
```

changedOutput schema / (root)

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

First observedv0.4.1Jun 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by naming the directory and the platform-dependent default glob, but it does not go beyond that. With annotations doing most of the safety disclosure, a 3 is appropriate.

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, well-structured sentence that leads with the core action and resource, then adds the platform-specific detail. There is no filler, and every part of the sentence earns its place.

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 low-complexity read-only listing tool, the description plus the fully documented schema and the provided output schema are sufficient. The directory, defaults, and parameters are all covered, so nothing critical is missing for an agent to call this correctly.

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%, and the input schema already documents both 'pattern' and 'recurse' clearly, including the default glob behavior. The description repeats the platform-specific default rather than adding new parameter meaning, so the baseline of 3 applies.

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 uses a specific verb ('List'), names the exact resource ('compiled EAs in Experts/'), and clarifies the platform-specific default patterns (*.ex5 for MT5, *.ex4 for MT4). This clearly distinguishes it from sibling list tools like list_snapshots, list_terminals, and list_backtests.

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 establishes a clear context: it is for listing compiled EAs in the Experts/ directory, with platform-aware defaults. It does not explicitly name alternatives or state when not to use it, but the scoping is strong enough that an agent can infer the right use case without confusion.

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