Skip to main content
Glama
Sign In
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_crossfader_context

Read-onlyIdempotent

Read Main crossfader value, native bounds, availability, automation, and all ordinary/Group/Return A/B assignments plus Group relationships without changing playback, selection, or mixer state.

Instructions

Read Main crossfader value, native bounds, availability and automation plus every ordinary/Group/Return A/B assignment and Group relationship. Unsupported fields remain explicit. No playback, selection or mixer changes; all profile.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "assignmentChoices": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "position": {
+        "type": "object"
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "tracks": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "transport": {
+        "type": "object"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "setFingerprint",
+      "position",
+      "tracks",
+      "assignmentChoices",
+      "transport",
+      "identityToken"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail: unsupported fields are returned explicitly and no playback, selection, or mixer state is altered. It does not explain auth or limits, but those are not material here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the read target and field list. 'Unsupported fields remain explicit' and 'all profile' are slightly opaque, but the description remains efficient.

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?

With a rich output schema, zero parameters, and strong annotations, the description supplies the right amount of scope: what state is read, that unsupported fields are explicit, and that nothing is mutated. It is complete enough for an agent to select and invoke it safely.

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?

There are zero input parameters, so the schema imposes no parameter-semantics burden; the baseline is 4. The description appropriately does not invent parameters and instead focuses on returned state.

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?

Opens with a specific verb ('Read') and resource ('Main crossfader'), then enumerates exactly which fields are returned: value, native bounds, availability, automation, A/B assignments, and Group relationships. This clearly distinguishes it from the mutation sibling set_crossfader_state and from broader mixer-context tools.

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?

Frames the tool as a read-only inspection of crossfader state and explicitly says it makes no playback, selection, or mixer changes. However, it does not explicitly name set_crossfader_state or state when to prefer other mixer-context siblings, so routing is implied by 'Read' rather than spelled out.

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

Deploy Server

Other Tools