Skip to main content
Glama
PHUICMT

mcp-mt5

by PHUICMT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tail_log

Read-onlyIdempotent

Tail MetaTrader log files to inspect EA live logs, daily Experts journal, or latest tester journal. Use tester mode after backtests to see runtime errors and effective test period.

Instructions

Tail a MetaTrader log: the EA's LiveLog.txt, the daily Experts journal, or the latest tester journal.

Use mode="tester" right after a backtest to see runtime errors and the effective test period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoJournal date as YYYYMMDD; defaults to today.
modeNo"live" = MQL5/Files/LiveLog.txt written by the EA, "journal" = MQL5/Logs/YYYYMMDD.log (Experts tab), "terminal" = logs/YYYYMMDD.log (Journal tab: connection, tester start), "tester" = newest Tester/logs file.live
linesNoNumber of lines from the end of the file.
structuredNoParse journal lines into {ts, source, message} records (journal/tester modes).

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 / date / description
      Added value: +"Journal date as YYYYMMDD; defaults to today."
    • addedInput schema / properties / lines / description
      Added value: +"Number of lines from the end of the file."
    • addedInput schema / properties / mode / description
      Added value: +"\"live\" = MQL5/Files/LiveLog.txt written by the EA, \"journal\" = MQL5/Logs/YYYYMMDD.log (Experts tab), \"terminal\" = logs/YYYYMMDD.log (Journal tab: connection, tester start), \"tester\" = newest Tester/logs file."
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "live",
+  "journal",
+  "terminal",
+  "tester"
+]
    • addedInput schema / properties / structured / description
      Added value: +"Parse journal lines into {ts, source, message} records (journal/tester modes)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "tail_logDictOutput",
+  "type": "object"
+}
  2. First observedv0.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, lowering the burden on the description. The description adds valuable behavioral context by identifying the exact log paths/sources and noting that tester mode reveals the effective test period. 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.

Conciseness5/5

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

The description is two short sentences with no filler. The core purpose is front-loaded, and the tester-mode hint adds practical value without bloating the definition.

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

Completeness4/5

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

With zero required parameters, an existing output schema, and annotations covering safety, the description covers the main use cases well. It omits the 'terminal' mode in the prose, but the schema already documents that mode, so the gap is minor.

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%, so the schema already documents all four parameters in detail. The description reinforces the tester mode usage but does not add meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 ('Tail') with a clear resource ('a MetaTrader log') and enumerates the three distinct sources (EA LiveLog.txt, daily Experts journal, latest tester journal). This maps cleanly to the mode enum and separates the tool from unrelated siblings.

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 explicitly advises using mode='tester' right after a backtest to see runtime errors and the effective test period, which is a concrete usage guideline. It doesn't name alternative tools or say when not to use tail_log, but the provided context is clear and actionable.

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