Skip to main content
Glama
Sign In
mt5-mcp

mt5-mcp

by ramanthind02
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_snapshot

Read-only

Read a snapshot manifest to retrieve EA sources, tester inputs, and the report path needed for backtest review.

Instructions

Read one snapshot manifest: EA sources, tester inputs, and the report path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "read_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value by naming the manifest's contents (EA sources, tester inputs, report path), but it says nothing about path semantics, error behavior for missing manifests, or size of the returned source payload.

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 with the verb first and the payload contents following the colon; nothing is wasted or padded.

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?

For a single-parameter read tool with no output schema, the description compensates reasonably by enumerating the manifest fields an agent will receive. The remaining gap is the undefined 'path' argument and no hint about how paths are produced, which keeps it just short of complete.

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 0% and the sole parameter 'path' is a bare string with no title or description. The description never clarifies whether 'path' is a snapshot directory, a manifest file, or a snapshot id, so the one thing an agent must get right is left undefined.

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?

States a specific verb and resource ('Read one snapshot manifest') and enumerates what the manifest contains (EA sources, tester inputs, report path), which separates it from list_snapshots. It does not explicitly name the sibling it complements, but the singular 'one snapshot' framing makes the distinction readable.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite or ordering hint (e.g., call list_snapshots first to obtain a path), and no mention of alternatives such as read_inputs or read_report. Usage is only implied by the word 'one'.

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