senti-mcp-server

List strategies deployed on an account

list_account_strategies

Read-only

List all expert advisors deployed on an MT5 account, returning symbol, timeframe, and status for each. Provide account id (not login) to see deployments.

Instructions

List the strategies (expert advisors) currently deployed on one MT5 account, with each deployment's symbol, timeframe and status. accountId is the id field from list_accounts — NOT login, which is the MT5 account number and is not a valid accountId. For the platform-wide catalog of strategies available to deploy, use list_strategies instead.

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
`strategies`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.9.0Sep 16, 2026
- removedOutput schema / properties / strategies / items / properties / chartId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / strategies / items / properties / chartId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / strategies / items / properties / mt5Account / properties / label / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / strategies / items / properties / mt5Account / properties / label / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Addedv1.2.0Aug 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint, so the description does not need to repeat safety properties. It adds useful behavioral context beyond them by clarifying that this returns only strategies deployed on the account and that accountId must be the id field, not the MT5 login. The description is consistent with the annotations and does not contradict them.

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 compact and front-loaded: the first sentence states what the tool does and what it returns, the second sentence prevents a common input error, and the third sentence routes to the sibling tool. Every sentence earns its place, with no filler or repetition of annotation properties.

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?

Given a single required parameter, an output schema, and annotations that cover the safety profile, the description provides everything an agent needs to call the tool correctly. It explains the output fields, clarifies the critical accountId semantics, and disambiguates against list_strategies. There is no meaningful gap in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents the accountId parameter at 100% coverage, so the baseline is 3. The description goes further by explicitly warning that login is the MT5 account number and is not a valid accountId, and by tying accountId to the output of list_accounts. This adds practical meaning beyond the schema's simple field description.

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') and resource ('strategies (expert advisors) currently deployed on one MT5 account'), and even enumerates the output fields (symbol, timeframe, status). It clearly distinguishes this from the sibling list_strategies by saying that list_strategies is the platform-wide catalog.

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 for a different use case: 'For the platform-wide catalog of strategies available to deploy, use list_strategies instead.' It also clarifies the correct input source for accountId, telling the agent to take it from list_accounts rather than using the MT5 login, which prevents a common invocation error.

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

Deploy Server