Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_track_signal_activity

Read-onlyIdempotent

Read input/output peak-hold meters and control flags for 1-64 Ableton track, Group, Return, or Main IDs to check signal activity; no edits.

Instructions

Read native input/output peak-hold meters and control flags for one trackId, or 1-64 unique trackIds in one callback with shared transport and ordered tracks. Track, Group, Return and Main supported. Native 0–1; not dB, sample-synchronous audio, silence or speaker proof. Unavailable meters stay unknown. Includes bounded native Group ancestry and shared explicit track/Return solo context; unknown or limited context is explicit, not proof of routing or isolation. No edits; all profile.

Input Schema

NameRequiredDescriptionDefault
trackIdNotrack-N from list_tracks, return-N from get_set_mixer, or master.
trackIdsNoExact track/Group/Return/Main IDs in requested order; excludes trackId.

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": {
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "controls": {
+        "type": "object"
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "meters": {
+        "type": "object"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "trackId": {
+        "type": "string"
+      },
+      "tracks": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "stateVersion"
+    ],
+    "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.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: batching 1–64 unique track IDs in one callback, ordered tracks, shared transport, bounded Group ancestry, shared solo context, and explicit unknown or limited context. It also clarifies that the values are native 0–1 peak-hold data and not proof of silence, speaker output, or isolation.

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?

The description is front-loaded with the core action and then layers in relevant limits and caveats. It is dense but mostly purposeful, with only minor jargon such as 'all profile' that could be clearer.

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 rich annotations, full schema description coverage, and an output schema, the description sufficiently covers scope, supported object types, numerical units, batching behavior, and ambiguity caveats. An agent has enough information to call the tool correctly without needing return-value details in the description.

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?

Schema coverage is 100%, so the schema already defines trackId and trackIds. The description adds useful semantics beyond the schema by explaining the one-or-many calling pattern, shared transport behavior, ordered tracks, and the 1–64 unique-ID batch limit.

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 gives a specific verb and resource: read native input/output peak-hold meters and control flags for one or many track IDs. It clearly scopes supported object types (Track, Group, Return, Main), though it does not explicitly name a sibling alternative for comparison.

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?

Usage is implied by the meter-reading purpose and caveats such as not being dB or sample-synchronous audio, but the description does not state when to prefer this over sibling context tools or when not to use it. The limitations help set expectations but stop short of explicit routing guidance.

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