Read Ableton Live bridge identity, capabilities, Set path, tempo, playback status, and current state version. Use this to inspect session state before issuing guarded control commands.
Read bridge identity, capabilities, Set path, tempo, playback and state version.
| 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": {
+ "bridgeVersion": {
+ "type": "string"
+ },
+ "capabilities": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "filePath": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "isPlaying": {
+ "type": "boolean"
+ },
+ "serverIdentity": {
+ "properties": {
+ "fileCount": {
+ "minimum": 1,
+ "type": "integer"
+ },
+ "name": {
+ "type": "string"
+ },
+ "schemaVersion": {
+ "const": 1
+ },
+ "sourceSha256": {
+ "pattern": "^[a-f0-9]{64}$",
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "schemaVersion",
+ "name",
+ "version",
+ "sourceSha256",
+ "fileCount"
+ ],
+ "type": "object"
+ },
+ "setFingerprint": {
+ "type": "string"
+ },
+ "stateVersion": {
+ "minimum": 1,
+ "type": "integer"
+ },
+ "tempo": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "stateVersion",
+ "setFingerprint"
+ ],
+ "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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered without the description. The description contributes the inventory of returned values, but adds no behavioral context such as whether the state version is monotonic or how often the snapshot refreshes. With annotations carrying the main burden, a 3 is appropriate.
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?
A single dense sentence with the verb first and the returned fields enumerated in priority order. No filler, no repetition of the tool name meaninglessly.
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?
With zero parameters, a rich annotation set, and an output schema that documents the return shape, the description only needs to signal the scope of the snapshot, which it does. Only a hint about when in a workflow to invoke it is missing.
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 takes zero parameters, so the baseline is 4. The schema is empty and complete for the tool's contract; nothing about parameters needs explaining.
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 verb 'Read' plus an explicit enumeration of the resource contents (bridge identity, capabilities, Set path, tempo, playback, state version) tells an agent precisely what comes back. It is distinguishable from domain-specific siblings like get_transport_context or get_set_mixer because it returns bridge-level metadata and a state version that no sibling does. It stops short of naming that distinction explicitly.
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?
There is no statement of when to call this versus the many other get_* context tools, nor any sequencing guidance (e.g., call first on connect, or use state version for change detection). Usage must be inferred from the field list alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.