Skip to main content
Glama
Sign In
mt5-mcp

mt5-mcp

by ramanthind02
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_symbols

Read-only

List broker symbol names available on the active MetaTrader 5 terminal, optionally filtered by group and capped by a limit. Use it to discover which instruments you can pull bar and tick history for.

Instructions

List symbol names on the active terminal. limit=0 returns every name.

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": "list_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 safety is covered; the description adds only the limit=0 semantics. It never mentions the default cap of 500, pagination behavior, or what the call returns, so it adds modest value beyond structured data.

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?

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the limit edge case. Nothing is redundant.

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

Completeness3/5

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

This is a simple read tool with no output schema, so extensive documentation is not required, but the unexplained 'group' parameter and undocumented default limit leave real gaps. An agent could invoke it, but could not use it correctly with grouping or predict truncation at 500 results.

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%, so the description must carry both parameters. It partially explains limit (limit=0 means unbounded) but is silent on the default 500 cap and gives no meaning at all for the 'group' parameter, leaving one of two params fully opaque.

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 ("List symbol names") plus the scope "on the active terminal", which separates it from siblings like list_terminals or symbol_info. It does not explicitly name a sibling it is not, but the resource is unambiguous.

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

Usage Guidelines3/5

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

The phrase "on the active terminal" implies a prerequisite (a terminal must be selected via use_terminal), but the description never says when to choose this over symbol_info or select_symbol. Usage is only inferable.

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