Skip to main content
Glama
Sign In
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_plugin_integration_context

Read-onlyIdempotent

Inspect loaded Serum 2, Omnisphere, or VPS Avenger plugins to check installed variants, controls, NKS counts, browser limits, and hidden state that Live loading does not verify.

Instructions

Inspect loaded Serum 2/Omnisphere/VPS Avenger: installed variants, controls, NKS counts, browser limits and Live UI save/User Library load. Loading in Live does not verify hidden plug-in state.

Input Schema

NameRequiredDescriptionDefault
trackIdYestrack-N from list_tracks, return-N from get_set_mixer, or master.
deviceIdYesID from list_devices.

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": {
+      "device": {
+        "type": "object"
+      },
+      "installedVariants": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "parameterExposure": {
+        "type": "object"
+      },
+      "profile": {
+        "type": "object"
+      },
+      "recommendedVariant": {
+        "anyOf": [
+          {
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "trackId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "trackId",
+      "device",
+      "profile",
+      "installedVariants",
+      "recommendedVariant",
+      "parameterExposure"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed3 schema fields changedv0.3.0
    • changedInput schema / properties / deviceId / description
      Previous value: -"Stable device ID returned by list_devices."New value: +"ID from list_devices."
    • changedInput schema / properties / trackId / description
      Previous value: -"Stable device-owner ID: track-N from list_tracks, return-N from get_set_mixer, or master."New value: +"track-N from list_tracks, return-N from get_set_mixer, or master."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context about which plugin integration details are inspected and warns that Live loading alone does not verify hidden plug-in state, though it does not discuss permissions or error behavior.

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?

Two tightly packed sentences front-load the inspection purpose and follow with a useful caveat. The colon-delimited list is efficient, though some entries are dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, complete parameter descriptions, and read-only annotations, the description only needs to convey scope and key caveats. It does that well, but it could better connect the tool to sibling device-inspection tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so trackId and deviceId are already documented in the input schema. The description does not add any parameter-level meaning beyond the schema, which meets the baseline 3 for high-coverage schemas.

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?

States a specific read/inspection action for loaded Serum 2, Omnisphere, and VPS Avenger and names the details exposed (variants, controls, NKS counts, browser limits, UI save/User Library load). It is clearly narrower than generic device tools, though it never names a sibling tool 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?

The caveat that loading in Live does not verify hidden plug-in state implies this tool should be used to inspect that hidden state, giving some usage context. However, it provides no explicit 'use this when...' guidance or alternatives such as get_device_hierarchy or list_devices.

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