ableton-mcp

Overview Schema Source Related Servers Discussions Admin

list_live_scales

Read-onlyIdempotent

Retrieve Ableton Live 12 scale names with semitone intervals and musical families to select exact scales for projects. Read-only.

Instructions

List Ableton Live 12 scale names with semitone intervals and musical families for exact scale selection. Read-only.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.3.1Oct 23, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "scales": {
+        "items": {
+          "properties": {
+            "family": {
+              "type": "string"
+            },
+            "intervals": {
+              "items": {
+                "maximum": 11,
+                "minimum": 0,
+                "type": "integer"
+              },
+              "minItems": 1,
+              "type": "array"
+            },
+            "name": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "family",
+            "intervals"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "scales"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "scales": {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "family": {
-          "type": "string"
-        },
-        "intervals": {
-          "items": {
-            "maximum": 11,
-            "minimum": 0,
-            "type": "integer"
-          },
-          "minItems": 1,
-          "type": "array"
-        },
-        "name": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "name",
-        "family",
-        "intervals"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "scales"
-]
```

Changed2 schema fields changedv0.3.0Oct 19, 2026

removedInput schema / required
```
Removed value: -[]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "scales": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "family": {
+            "type": "string"
+          },
+          "intervals": {
+            "items": {
+              "maximum": 11,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "minItems": 1,
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "family",
+          "intervals"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "scales"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description's 'Read-only' sentence repeats the annotation rather than adding behavioral context such as connection requirements, return behavior, or limitations.

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 front-loaded and appropriately sized: one substantive sentence states the resource and returned fields, followed by a short safety note. There is no unnecessary elaboration.

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 list tool with rich annotations and an output schema, the description provides enough context: it states the Live version, scale-name scope, included interval/family data, and selection-oriented purpose.

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 tool has zero parameters, so parameter semantics are inherently simple. The empty input schema and 100% schema description coverage mean the description does not need to explain parameter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: list Ableton Live 12 scale names, including semitone intervals and musical families. It is clear what the tool returns, but it does not explicitly distinguish itself from the similar sibling get_live_scale_reference.

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

Usage Guidelines3/5

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

The phrase 'for exact scale selection' implies when the tool is useful, but the description gives no explicit when-to-use versus when-not-to-use guidance and does not name an alternative such as get_live_scale_reference.

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

Deploy Server