Read master and return-bus mixer levels, sends, and routing from the current Ableton Live Set to check mix settings.
Read master and return-bus mixer levels, sends, and routing from the current Live Set.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Output schema / additionalPropertiesRemoved value: -trueOutput schema / anyOfAdded value: +[
+ {
+ "properties": {
+ "master": {
+ "properties": {
+ "mute": {
+ "type": "boolean"
+ },
+ "pan": {
+ "properties": {
+ "automationState": {
+ "type": "object"
+ },
+ "decibels": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "displayValue": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "enabled": {
+ "type": "boolean"
+ },
+ "max": {
+ "type": "number"
+ },
+ "min": {
+ "type": "number"
+ },
+ "silent": {
+ "type": "boolean"
+ },
+ "value": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "value"
+ ],
+ "type": "object"
+ },
+ "sends": {
+ "items": {
+ "properties": {
+ "decibels": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "returnTrackId": {
+ "type": "string"
+ },
+ "silent": {
+ "type": "boolean"
+ },
+ "value": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "value"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "solo": {
+ "type": "boolean"
+ },
+ "trackId": {
+ "type": "string"
+ },
+ "volume": {
+ "properties": {
+ "automationState": {
+ "type": "object"
+ },
+ "decibels": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "displayValue": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "enabled": {
+ "type": "boolean"
+ },
+ "max": {
+ "type": "number"
+ },
+ "min": {
+ "type": "number"
+ },
+ "silent": {
+ "type": "boolean"
+ },
+ "value": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "value"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [],
+ "type": "object"
+ },
+ "returns": {
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "mute": {
+ "type": "boolean"
+ },
+ "pan": {
+ "properties": {
+ "automationState": {
+ "type": "object"
+ },
+ "decibels": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "displayValue": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "enabled": {
+ "type": "boolean"
+ },
+ "max": {
+ "type": "number"
+ },
+ "min": {
+ "type": "number"
+ },
+ "silent": {
+ "type": "boolean"
+ },
+ "value": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "value"
+ ],
+ "type": "object"
+ },
+ "sends": {
+ "items": {
+ "properties": {
+ "decibels": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "returnTrackId": {
+ "type": "string"
+ },
+ "silent": {
+ "type": "boolean"
+ },
+ "value": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "value"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "solo": {
+ "type": "boolean"
+ },
+ "trackId": {
+ "type": "string"
+ },
+ "volume": {
+ "properties": {
+ "automationState": {
+ "type": "object"
+ },
+ "decibels": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "displayValue": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "enabled": {
+ "type": "boolean"
+ },
+ "max": {
+ "type": "number"
+ },
+ "min": {
+ "type": "number"
+ },
+ "silent": {
+ "type": "boolean"
+ },
+ "value": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "value"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "stateVersion": {
+ "minimum": 1,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "stateVersion",
+ "master",
+ "returns"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "error": {
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "outcome": {
+ "enum": [
+ "unknown",
+ "not_executed"
+ ]
+ }
+ },
+ "required": [
+ "message",
+ "outcome"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+]v0.3.0Input schema / requiredRemoved value: -[]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful specifics about what is read: master and return-bus levels, sends, and routing from the current Live Set. A lower score is not warranted because it does not contradict annotations and it adds meaningful scope beyond them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It states the action, scope, and relevant mixer data in one pass.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, rich read-only/idempotent annotations, and an output schema, the description provides enough context to call the tool correctly. It could be slightly more complete by explicitly stating that this reads all return buses and the master bus rather than a single track, but the core information is present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. Schema coverage is 100% and there are no parameters to document, so no compensation in the description is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb plus resource ('Read master and return-bus mixer levels, sends, and routing') and scopes it to the current Live Set. It distinguishes this from track-level mixer reads implied by siblings like get_track_mixer, though it does not explicitly name that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Read-only usage is implied by 'Read', but there is no explicit when-to-use vs when-not-to-use guidance or named alternatives such as get_track_mixer, set_master_mixer, or set_return_mixer. The scope is clear enough that an agent can infer this is for reading the master/return bus, not modifying it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.