senti-mcp-server

List deployable strategies

list_strategies

Read-only

Review every strategy available to deploy on Senti Quant, with supported symbols, timeframes, ratings, and presets. Use the returned id as eaDefinitionId to deploy.

Instructions

List every strategy (expert advisor) available to deploy on Senti Quant, with its supported symbols, timeframes, rating and presets. This is the platform-wide catalog of what COULD be deployed — it is NOT what is currently running on an account. For the strategies running on a specific account, use list_account_strategies. Use id as eaDefinitionId when deploying.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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 / avgRating / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / strategies / items / properties / avgRating / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / strategies / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / strategies / items / properties / description / 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=true and openWorldHint=true, covering the safety and open-world nature of the call. The description adds useful behavioral context beyond annotations: it returns what COULD be deployed, not what is running, lists the included fields (symbols, timeframes, rating, presets), and explains id semantics. It could mention pagination or rate limits, but with zero parameters and an output schema, the burden is low.

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?

Three sentences with every clause earning its place: the core action and contents, the scope warning, and the sibling routing plus deployment hint. It is front-loaded with the most important information and contains no filler.

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 operation with an output schema and safety annotations, this description is complete. It explains scope, content, the key sibling distinction, and how the returned id should be used downstream. There are no material gaps for an agent to call it correctly.

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 has zero parameters, so the baseline is 4. The description still adds a meaningful semantic hint by telling agents to use `id` as `eaDefinitionId` when deploying, which helps connect this catalog to deployment even though the tool itself takes no parameters.

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 and resource: 'List every strategy (expert advisor) available to deploy on Senti Quant.' It explicitly says this is the platform-wide catalog, distinguishing it from list_account_strategies. An agent can immediately understand exactly what the tool returns and how it differs 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?

It clearly states when to use this tool: to see the platform-wide catalog of deployable EAs, not what is currently running. It names the alternative, list_account_strategies, for account-specific strategies, and gives a concrete deployment hint about using `id` as `eaDefinitionId`. No ambiguity remains.

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

Deploy Server