Skip to main content
Glama

get_open_positions

Returns open positions plus balance and equity from the latest snapshot for all or selected accounts, with optional filtering by magic number or symbol.

Instructions

Tüm (ya da seçilen) hesapların açık pozisyonlarını ve bakiye/equity'sini son snapshot'tan döner; magic/sembol ile süzülebilir.

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

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context by naming the data source ('son snapshot'), which tells the agent the values are point-in-time rather than streaming, and it discloses that balance/equity are returned alongside positions. It never explicitly says the operation is read-only and says nothing about refresh cadence, pagination, or what an empty result looks like.

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?

A single tight sentence with the core resource front-loaded ('açık pozisyonlarını ve bakiye/equity'sini') and the filter capability trailing. Every clause carries information, with only a minor parenthetical ('Tüm (ya da seçilen)') that adds little.

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?

For a read-only, 3-optional-parameter tool with no output schema and no annotations, the description covers what is returned and where it comes from. It leaves gaps an agent would care about: confirmation that the call is non-mutating, whether balance/equity is per-account in the response, and any behavior when accountId is omitted among many accounts.

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 three parameters (magic, symbol prefix matching, accountId) are already fully documented in the schema, setting the baseline at 3. The description adds only the aggregate signal that zero filters means all accounts and that magic/symbol act as filters; it contributes no new syntax or matching semantics beyond the schema.

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: returns open positions plus balance/equity for all or selected accounts, read from the latest snapshot, filterable by magic/symbol. The snapshot framing and the balance/equity payload give it a distinct identity. It does not explicitly contrast itself with the sibling `get_positions`, so it stops short of a 5.

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?

Implicit guidance is present: the tool is for open positions across all accounts by default, narrowed by accountId/magic/symbol. There is no explicit statement of when to prefer it over `get_positions`, no prerequisites, and no note that the data is a snapshot rather than live, which is exactly the condition an agent would want stated.

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