senti-mcp-server

List open positions on an account

list_positions

Read-only

Retrieve live open positions for a specified MT5 account, including symbol, direction, volume, entry and current price, stop loss, take profit, swap, and floating profit.

Instructions

List the positions currently open on one MT5 account, read live from the terminal: symbol, direction, volume, open and current price, stop loss, take profit, swap and floating profit. accountId is the id field from list_accounts — NOT login. Each position's ticket is the handle used to close it. An sl or tp of 0 means no stop loss or take profit is set.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`accountId`	Yes	The `id` field from list_accounts. Not the `login` (MT5 account number).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	Yes
`positions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.9.0Sep 16, 2026
- removedOutput schema / properties / positions / items / properties / sl / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / sl / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / positions / items / properties / tp / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / positions / items / properties / tp / type
```
Added value: +[
+  "number",
+  "null"
+]
```
Addedv1.2.0Aug 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds valuable behavioral context: it clarifies that sl/tp=0 means no stop loss/take profit is set, and that the ticket field is the handle for closing positions. It also reiterates the accountId caveat. These details go beyond the annotation's safety profile and help the agent interpret the output correctly.

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?

The description is two sentences with zero fluff. It front-loads the primary purpose, then delivers critical caveats about accountId, ticket, and sl/tp semantics. Every sentence earns its place, and the structure is highly scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (single parameter), has an output schema, and annotations covering safety. The description explains the return field semantics (sl/tp=0, ticket handle) and the accountId caveat, covering everything an agent needs to call it correctly and interpret results. No missing essential context for a read-only list operation.

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 coverage is 100% – the schema already describes accountId as the id field from list_accounts, not the login. The description repeats this caveat, adding no new semantic information. However, the description's explanation of output fields (ticket, sl/tp) indirectly reinforces the parameter's purpose. Baseline 3 is appropriate because the schema fully covers the parameter.

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?

The description clearly states the tool lists open positions on a single MT5 account, enumerates the returned fields (symbol, direction, volume, prices, SL/TP, swap, floating profit), and distinguishes it from siblings like list_pending_orders and list_deals by specifying 'open positions.' The verb and resource are explicit, and the 'read live from the terminal' phrase adds context.

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

Usage Guidelines4/5

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

The description provides clear context (positions currently open, live from terminal) and important usage guidance (accountId is the id field, not login; ticket is the close handle). It does not explicitly exclude alternatives like list_pending_orders or list_deals, but the resource distinction is sufficiently clear. The lack of an explicit when-not statement prevents a 5.

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

Deploy Server