senti-mcp-server

List MQL5 authoring drafts

list_drafts

Read-only

List your MQL5 drafts with compile status, sizes, and SHA-256 hashes to find a draft ID, spot broken builds, or verify a local copy is current.

Instructions

List the MQL5 drafts this API key owns, most recently updated first, with each draft's compile status, source size and SHA-256, compile-log size, attachment sizes and registered-EA id. Use it to find a draftId, to answer "what am I working on" and "which of my drafts are broken", or to tell whether a copy of a draft you hold is current. The list carries sizes and hashes rather than bodies: no source code, compiler log or diagnostics. A non-null compileLogBytes means the last compile left a log to read, even when diagnosticsCount is 0. Call get_draft for one draft's source, compiler log and diagnostics, and list_draft_attachments for its indicator sources.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	Yes
`drafts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv2.9.0Sep 16, 2026

addedOutput schema / properties / drafts / items / properties / attachments / items / properties / sourceBytes / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / drafts / items / properties / attachments / items / properties / sourceBytes / minimum
```
Added value: +-9007199254740991
```
changedOutput schema / properties / drafts / items / properties / attachments / items / properties / sourceBytes / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / drafts / items / properties / attachments / items / properties / updatedAt
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / drafts / items / properties / attachments / items / required

Previous value: -[
-  "id",
-  "filename",
-  "createdAt",
-  "sourceBytes"
-]New value: +[
+  "id",
+  "filename",
+  "sourceBytes",
+  "createdAt",
+  "updatedAt"
+]

addedOutput schema / properties / drafts / items / properties / compileLogBytes

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / drafts / items / properties / diagnosticsCount / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / drafts / items / properties / diagnosticsCount / minimum
```
Added value: +-9007199254740991
```
changedOutput schema / properties / drafts / items / properties / diagnosticsCount / type
```
Previous value: -"number"New value: +"integer"
```
removedOutput schema / properties / drafts / items / properties / eaDefinitionId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / drafts / items / properties / eaDefinitionId / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / drafts / items / properties / lastCompileStatus / anyOf

Previous value: -[
-  {
-    "enum": [
-      "PENDING",
-      "SUCCESS",
-      "FAILED"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "SUCCESS",
+      "FAILED"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / drafts / items / properties / logTruncated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / drafts / items / properties / sourceBytes / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / drafts / items / properties / sourceBytes / minimum
```
Added value: +-9007199254740991
```
changedOutput schema / properties / drafts / items / properties / sourceBytes / type
```
Previous value: -"number"New value: +"integer"
```
addedOutput schema / properties / drafts / items / properties / sourceSha256
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / drafts / items / required

Previous value: -[
-  "id",
-  "name",
-  "createdAt",
-  "updatedAt",
-  "lastCompileStatus",
-  "compiledUpToDate",
-  "eaDefinitionId",
-  "sourceBytes",
-  "diagnosticsCount",
-  "attachments"
-]New value: +[
+  "id",
+  "name",
+  "sourceBytes",
+  "sourceSha256",
+  "createdAt",
+  "updatedAt",
+  "lastCompileStatus",
+  "compileLogBytes",
+  "logTruncated",
+  "diagnosticsCount",
+  "compiledUpToDate",
+  "eaDefinitionId",
+  "attachments"
+]

Addedv2.8.0Aug 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark readOnlyHint, and the description adds meaningful behavior beyond that: the list carries sizes and hashes rather than bodies, and a non-null compileLogBytes is explained even when diagnosticsCount is 0. This gives the agent important interpretation context that annotations alone would not provide.

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 dense but well-organized: the core action and ordering are front-loaded, followed by use cases, payload constraints, and sibling routing. Every sentence adds useful selection or interpretation detail with 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 tool with an output schema, the description fully covers purpose, usage context, response content, and alternatives. An agent has everything needed to decide when to call it and how to interpret the results.

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 properties, so there are no parameter meanings for the description to clarify. The description appropriately focuses on what the response contains, which is the relevant semantic information for a parameterless listing tool.

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 the MQL5 drafts this API key owns'), specifies ordering ('most recently updated first'), and enumerates the returned fields. It also distinguishes itself from get_draft and list_draft_attachments by explicitly stating what it does not include.

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 provides concrete use cases: find a draftId, answer 'what am I working on' and 'which of my drafts are broken', or check if a held copy is current. It names the alternative tools for deeper content and tells the agent when to call them.

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

Deploy Server