Skip to main content
Glama

get_trades

List closed MetaTrader 5 trades newest first, including profit, swap, commission, and net results; filter by account, symbol, magic, or date and paginate with the returned cursor.

Instructions

Kapanan işlemleri listeler (en yeni önce): ticket, sembol, yön, lot, açılış/kapanış fiyatı ve zamanı, kâr, swap, komisyon, net, magic, yorum, hesap. Devamı için dönen nextCursor'ı cursor olarak verin.

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_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoKapanış zamanı bitiş (ISO)
fromNoKapanış zamanı başlangıç (ISO)
limitNoSayfa boyu (varsayılan 50)
magicNoMagic numarası ya da 'none' (magic'siz)
cursorNoÖnceki yanıtın nextCursor değeri
symbolNoSembol öneki, ör. XAUUSD (XAUUSDm, XAUUSDc eşleşir)
accountIdNoHesap id (list_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose result ordering (newest first), the field set returned, and the cursor/nextCursor pagination contract, which is real added value. It says nothing about read-only safety, permissions, cursor expiry, or whether the response is capped, so a mutation-adjacent agent still has to assume.

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 sentences, both earning their place: the first front-loads what is listed, ordering, and returned fields; the second states the pagination contract. No preamble, no repetition of the tool name, nothing extraneous.

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?

For a 7-parameter, no-annotation tool with no output schema, the description compensates well by enumerating returned fields and explaining nextCursor. Remaining gaps are minor: it does not say whether from/to are inclusive or in which timezone, nor what happens when filters are combined or when the result set is empty.

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?

Schema description coverage is 100%, so all seven parameters (from/to, limit, magic, cursor, symbol prefix, accountId) are already documented, including the XAUUSDm/XAUUSDc prefix-match behavior. The description adds the pagination loop (nextCursor -> cursor) but nothing else about filter combination or date/timezone semantics, so the schema does the heavy lifting.

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?

"Kapanan işlemleri listeler" gives a specific verb plus resource and scope (closed trades, newest first), which naturally separates it from get_open_positions/get_positions. It also enumerates the returned fields, so the agent knows what data it gets. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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 only explicit usage instruction is the pagination follow-up: pass the returned nextCursor as cursor. There is no guidance on when to choose this over get_positions/get_report, no note on prerequisites (e.g. accountId from list_accounts is only mentioned in the schema), and no exclusions. Usage is implied by the resource name rather than stated.

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