Skip to main content
Glama
PHUICMT

mcp-mt5

by PHUICMT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_tester_report

Read-onlyIdempotent

Parse MetaTrader Strategy Tester HTML reports into summary metrics and trades; retrieve full HTML via report URI.

Instructions

Parse a Strategy Tester HTML report (MT5 or MT4) into summary metrics; the full HTML stays behind report_uri.

Prefer passing the report_path returned by run_backtest/get_backtest; without path the newest report on disk is used, which may belong to an older run. summary values are the strings printed in the report ("10 000.00", "359.61 (3.34%)"); use compare_reports / regression_check for numeric comparison. Read the mt5://report/{id} resource only when you need the original HTML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoAbsolute path to a report .htm; defaults to the newest report found on disk.
max_tradesNoMax trade rows to return in `trades` when response_format="detailed".
raw_truncateNoCharacters of raw HTML to inline (0 = none; read report_uri instead).
response_formatNo"concise" = summary metrics + counts + report_uri; "detailed" adds the parsed trade rows.concise

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • addedInput schema / properties / max_trades
      Added value: +{
+  "default": 500,
+  "description": "Max trade rows to return in `trades` when response_format=\"detailed\".",
+  "title": "Max Trades",
+  "type": "integer"
+}
    • addedInput schema / properties / path / description
      Added value: +"Absolute path to a report .htm; defaults to the newest report found on disk."
    • changedInput schema / properties / raw_truncate / default
      Previous value: -50000New value: +0
    • addedInput schema / properties / raw_truncate / description
      Added value: +"Characters of raw HTML to inline (0 = none; read report_uri instead)."
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "\"concise\" = summary metrics + counts + report_uri; \"detailed\" adds the parsed trade rows.",
+  "enum": [
+    "concise",
+    "detailed"
+  ],
+  "title": "Response Format",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "read_tester_reportDictOutput",
+  "type": "object"
+}
  2. First observedv0.4.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds valuable behavior beyond them: the risky default of using the newest report without `path`, the fact that `summary` values are raw strings rather than numbers, and the distinction between this tool and reading the `mt5://report/{id}` resource directly.

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?

Three tightly packed sentences convey purpose, usage guidance, and caveats with zero fluff. The core function is front-loaded, followed by actionable alternatives and a warning about output types.

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?

The description sufficiently covers purpose, path selection, output semantics, and alternative tools. Combined with the input schema (100% parameter coverage) and an output schema, an agent has everything needed to select and invoke this tool correctly.

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?

Schema description coverage is 100% for all four parameters, so the baseline is 3. The description adds useful context for `path` (prefer backtest-returned path; fallback can be stale) and for `raw_truncate` (read `report_uri` instead for full HTML), which elevates it above the baseline.

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 and resource: 'Parse a Strategy Tester HTML report (MT5 or MT4) into `summary` metrics'. It also states what it does not do (the full HTML stays behind `report_uri`), which distinguishes it from sibling tools like `read_optimization` or `compare_reports`.

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?

Explicit guidance is given on when to use this tool: 'Prefer passing the `report_path` returned by `run_backtest`/`get_backtest`'. It also names alternatives for related tasks ('use `compare_reports` / `regression_check` for numeric comparison') and warns against the default fallback behavior ('newest report on disk... may belong to an older run').

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