Skip to main content
Glama

get_report

Summarize closed MetaTrader 5 trades by account, date range, symbol, or magic, returning totals, win/loss counts, gross/net profit and daily net breakdown.

Instructions

Kapanan işlemlerin özeti (panel Rapor sayfası): toplam işlem/kazanan/kaybeden/brüt kâr-zarar/net, magic bazında kırılım ve günlük net. Net = kâr + swap + komisyon (hesap para biriminde; cent hesapta USC).

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

Input Schema

NameRequiredDescriptionDefault
toNoKapanış zamanı bitiş (ISO)
tzNoGünlük kırılım için IANA saat dilimi (varsayılan UTC)
fromNoKapanış zamanı başlangıç (ISO)
magicNoMagic numarası ya da 'none' (magic'siz)
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

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose valuable domain behavior: only closed trades are counted, and net is defined as profit + swap + commission in the account currency (USC on cent accounts), which prevents real misinterpretation of the numbers. It does not state that the call is a read-only operation, whether there are limits on the date span, or anything about result size, so it is helpful but incomplete.

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?

One compact sentence with the core purpose front-loaded, then the metric list, then the net formula. Every clause adds information and there is no filler. The dense parentheticals reduce readability slightly, but nothing is redundant.

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?

There is no output schema, and the description compensates by enumerating the reported figures and defining net, so an agent knows what comes back. Combined with complete schema parameter documentation, the definition is close to self-sufficient. Missing are only secondary details like the default scope when from/to are omitted and whether results are paginated.

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 six parameters (from, to, tz, magic, symbol, accountId) are already documented in the schema. The description adds only indirect meaning, e.g. 'günlük net' hints that tz drives the daily bucketing, and 'magic bazında kırılım' hints that magic filters or groups. This is the baseline case where 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?

The description names a specific resource and scope: a summary report over closed trades ('Kapanan işlemlerin özeti'), with the exact metrics returned (total/winning/losing trades, gross and net P&L, breakdown by magic, daily net). This clearly separates it from raw-list siblings such as get_trades or get_positions. It stops short of a direct 'use this instead of X' contrast, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that aggregates come from get_report while per-trade rows come from get_trades. Nothing is misleading, but the routing guidance is essentially absent.

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