mql5-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_referenceA | Search the official MQL5 (MetaTrader 5) function reference by name or section. Returns up to 10 matches with signatures and doc links. Use before writing MQL5 calls to avoid MQL4 syntax or invented functions. |
| get_signatureA | Get the exact MQL5 signature(s), section and official doc link for one function, e.g. CopyBuffer or OrderSend. |
| explain_codeA | Explain an MQL5 trade server return code (MqlTradeResult.retcode, e.g. 10016) or runtime error (GetLastError(), e.g. 4014) by number or constant name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
search_reference and get_signature both target function lookups and could be confused at the margins, but the multi-match search vs. single exact-signature semantics are described clearly. explain_code is entirely distinct, targeting return codes and runtime errors.
All three tools use a consistent snake_case verb_noun pattern (search_reference, get_signature, explain_code) with clear, predictable action verbs. No mixing of conventions or styles.
Three focused tools is on the lean side but each earns its place covering search, lookup, and error decoding. Slightly thin for a documentation server that could also expose browsing or content retrieval.
Search, signature lookup, and error explanation are covered, but there is no way to retrieve full documentation text, code examples, or enumerate functions within a section. These gaps force agents to rely only on signatures and external links.