Skip to main content
Glama

My MT5 account

get_my_mt5_account
Read-only

The authenticated user's connected MT5 account (via the SocialForex MT5 Bridge EA): balance, equity, free margin, open positions, pending orders and the last queued commands with their status. Requires a personal SocialForex API token. Create one at /mt5 (section "Connect an AI assistant (MCP)") and add it to the MCP client as header Authorization: Bearer sfmcp_....

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds genuine context by stating a personal SocialForex API token is required and exactly how to pass it (Authorization: Bearer sfmcp_...). It does not mention data freshness or what happens if the bridge EA is offline, which are the remaining behavioral gaps.

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?

Two sentences, front-loaded with the resource and its returned fields, followed by the auth prerequisite. The enumerated field list is dense but each item is informative; the token-setup sentence is operational detail that could be trimmed but still earns its place for first-time callers.

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 no output schema, the description carries the burden of describing return content, and it does so by naming the six data categories returned. It omits freshness/staleness semantics and error behavior when no MT5 account is connected, which matters for an EA-bridged, open-world read.

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

Parameters4/5

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

The tool takes no parameters, so the baseline is 4. The description correctly implies a parameterless, account-scoped call with no filtering options, leaving nothing ambiguous about invocation.

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?

Names the exact resource (the authenticated user's connected MT5 account via the SocialForex bridge) and enumerates what it returns: balance, equity, free margin, open positions, pending orders, and queued command status. This is clearly distinguishable from siblings like place_mt5_order (a mutation) or get_quotes (market data).

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?

Usage is only implied: an agent can infer this is the state-read tool to call before or after placing orders, but the description never states when to use it versus alternatives such as get_quotes or place_mt5_order. It does supply the authentication prerequisite and where to obtain a token, which is practical setup guidance rather than selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.