senti-mcp-server

List pending orders on an account

list_pending_orders

Read-only

List unfilled limit and stop orders on an MT5 account, displaying each order's symbol, type, volume, trigger price, stop loss, and take profit to track or cancel pending trades.

Instructions

List the pending limit and stop orders resting on one MT5 account, read live from the terminal: symbol, order type, volume, trigger price, stop loss and take profit. These are orders that have NOT been filled — for filled positions currently open, use list_positions. accountId is the id field from list_accounts, NOT login. Each order's ticket is the handle used to cancel it. An sl, tp or priceStopLimit of 0 means that level is not 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
`orders`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds substantial context beyond that: the data is 'read live from the terminal' (volatility/freshness), the 'NOT been filled' scope constraint, that each order's `ticket` is the handle used to cancel it, and the crucial semantics that an `sl`, `tp`, or `priceStopLimit` of 0 means the level is unset. This materially enriches what an agent needs to interpret results correctly.

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?

The description is a dense multi-sentence block, but every sentence earns its place: scope, returned fields, the exclusion of filled orders, the accountId clarification, ticket usage, and zero-value semantics. It is appropriately sized for the information it carries, though it front-loads the core purpose well in the opening clause. No filler or redundancy.

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?

The tool has an output schema (so return values need no elaboration) and annotations covering the safety profile. The description covers what is returned, what is excluded, accountId semantics, ticket-as-cancellation-handle usage, and zero-value field meanings. For a single-parameter list tool, essentially everything an agent needs to call it correctly and interpret results is present.

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% — the schema itself already documents accountId as 'The `id` field from list_accounts. Not the `login` (MT5 account number).' The description repeats this same guidance ('accountId is the id field from list_accounts, NOT login') without adding new information. This is useful reinforcement but adds no value beyond the schema, so the baseline 3 is appropriate.

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 states a specific verb ('List'), a precise resource ('pending limit and stop orders resting on one MT5 account'), and the scope ('one MT5 account', 'read live from the terminal'). It enumerates the returned fields (symbol, order type, volume, trigger price, stop loss, take profit) and explicitly distinguishes itself from list_positions by clarifying these are unfilled orders. This fully differentiates it from siblings.

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

Usage Guidelines5/5

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

The description explicitly names the alternative tool (list_positions) and the condition that selects it ('for filled positions currently open'). It also disambiguates the accountId parameter by warning it is the `id` field from list_accounts, NOT `login`. Both the when-to-use and the common pitfall are addressed explicitly.

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

Deploy Server