senti-mcp-server

List linked MT5 accounts

list_accounts

Read-only

Lists MT5 trading accounts linked to your Senti Quant API key, showing each account's ID, login, broker, balance, equity, sync state, and running strategies. Pass the ID to other Senti endpoints.

Instructions

List the MT5 trading accounts linked to the configured Senti Quant API key. Returns each account's id, login, broker, last known balance and equity, sync state, and running strategies. The id field is the accountId every other Senti endpoint takes — pass id, not login, when a tool asks for an account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`accounts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv2.9.0Sep 16, 2026

removedOutput schema / properties / accounts / items / properties / brokerAccountTypeName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / accounts / items / properties / brokerAccountTypeName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / accounts / items / properties / label / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / accounts / items / properties / label / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / accounts / items / properties / lastKnownBalance / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / accounts / items / properties / lastKnownBalance / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / accounts / items / properties / lastKnownEquity / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / accounts / items / properties / lastKnownEquity / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / accounts / items / properties / lastSyncAt / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / accounts / items / properties / lastSyncAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / accounts / items / properties / server / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / accounts / items / properties / server / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / accounts / items / properties / terminal / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "assignedPort": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "nodeName": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "terminalStatus": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "assignedPort",
-      "terminalStatus",
-      "nodeName"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "assignedPort": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "nodeName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "terminalStatus": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "assignedPort",
+      "terminalStatus",
+      "nodeName"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv0.1.0Aug 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=trueabc and openWorldHint=true, so the read-only safety profile is covered. The description adds meaningful behavioral context by stating exactly what each returned account entry contains and that `id` is the accountId used by other endpoints, which goes beyond the structured annotations.

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 no filler: the first states the action and scope, the second lists the output fields and adds the critical id/login distinction. Every sentence provides necessary information and the most important usage detail is front-loaded.

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?

For a zero-parameter, read-only list tool with an output schema, the description is complete. It identifies the resource, the output fields, and the cross-tool meaning of `id`. No additional pagination or ordering details are necessary for correct invocation.

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?

Parameter count is 0 and schema coverage is 100%, so the baseline is 4. The description goes further by explaining the meaning and downstream use of the returned `id` field, which is effectively the most important semantic information an agent needs for parameterizing future calls.

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?

States a specific verb ('List') and a specific resource ('MT5 trading accounts linked to the configured Senti Quant API key'), then enumerates the returned fields. It clearly differentiates from siblings like list_brokers and list_account_strategies by identifying exactly which account-level data is returned.

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 makes the tool's role obvious: it is the way to discover linked MT5 accounts and obtain the canonical accountId. It gives downstream guidance ('pass id, not login') that helps an agent choose and use the result correctly. It does not explicitly name sibling alternatives or exclusions, but the context is otherwise clear.

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

Deploy Server