Skip to main content
Glama

get_positions

Retrieve open positions and the latest balance/equity for a specified MT5 account by providing its accountId from list_accounts.

Instructions

Belirli bir MT5 hesabının açık pozisyonlarını ve son bakiye/equity değerini döner. accountId list_accounts'tan alınır.

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": {
      "accountId": "<accountId>"
    },
    "name": "get_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesMT5 hesap id (list_accounts'tan)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does disclose the response content (open positions plus balance/equity), which is helpful, but it never states that the operation is read-only, whether it has side effects, what happens for an unknown or disconnected account, or how stale the balance/equity value may be.

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 short sentences with no filler, and the primary output description is front-loaded ahead of the input provenance note. Nothing is redundant or padded. It is slightly under-specified rather than verbose, but the structure is clean.

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?

With no output schema and no annotations, the description must cover both return content and behavior; it covers the return content briefly but leaves safety, failure modes, and freshness unstated. Most importantly, it does not resolve the overlap with the closely named sibling get_open_positions. Adequate but with clear gaps.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage, so the schema already documents accountId and its UUID format. The description repeats the same provenance note ('list_accounts'tan') without adding format, validation, or example detail beyond the schema. Baseline 3 applies when the schema does the work.

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+resource pair: returns the open positions plus the latest balance/equity for a given MT5 account. That is concrete and understandable. However, it never distinguishes itself from the sibling 'get_open_positions', which sounds nearly identical, so an agent cannot tell the two apart from the description alone.

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?

It supplies one useful prerequisite: the accountId comes from list_accounts, which tells the agent how to obtain the required input. It gives no guidance on when to prefer this tool over get_open_positions or get_trades, and no exclusions or context conditions are stated.

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