Skip to main content
Glama
Sign In
TradeLab-MCP

TradeLab-MCP

by CaioAllgayer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

select_terminal

Switch the active MetaTrader terminal data folder for this session, allowing backtests to run against a chosen terminal installation.

Instructions

Switch the active terminal data folder for this session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "select_terminal"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashNo
originNo
editionNomt5
installNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavior disclosure burden. 'Switch' implies a state-changing operation and 'for this session' implies non-persistence, but the description does not explain what happens when parameters are null, whether validation occurs, or what side effects changing the active terminal may have.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no filler or redundancy. It earns its place by conveying the core action and scope, though it is quite terse.

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

Completeness2/5

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

For a tool with four optional parameters, no output schema, and no annotations, this description is incomplete. It leaves ambiguous how to specify the terminal, what the result of switching is, and what happens with invalid or missing input, making correct invocation unlikely without external knowledge.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the four parameters (hash, origin, edition, install). An agent has no way to know how these parameters identify a terminal, which combination is required, or what defaults mean beyond the schema's bare values.

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?

The description states a specific verb and resource: 'Switch the active terminal data folder for this session.' It clearly indicates what the tool does and adds session scoping, but it does not explicitly differentiate itself from sibling tools like list_terminals or kill_terminal.

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?

The only usage hint is 'for this session,' which implies a temporary, session-scoped action. There is no guidance about when to choose this tool over alternatives, no prerequisites, and no mention that list_terminals should be called first to discover available terminals.

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