Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_project_media

Read-onlyIdempotent

Inspect saved Ableton Live 12 project sample references and file contents. Reports missing, ambiguous, or external samples and distinguishes saved snapshots from unsaved Live edits.

Instructions

Inspect saved Live 12 sample references and file contents in the current Project. Reports missing, ambiguous and external samples; distinguishes the saved snapshot from unsaved Live edits. Does not certify plug-in libraries, licenses, Max dependencies or other Sets. Requires macOS English Live for native clean-state observation.

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": {
+      "completePortabilityVerified": {
+        "const": false
+      },
+      "deviceDependencies": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "file": {
+        "type": "object"
+      },
+      "native": {
+        "type": "object"
+      },
+      "project": {
+        "type": "object"
+      },
+      "samples": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "savedSnapshotMatchesLive": {
+        "type": "boolean"
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "setFingerprint",
+      "file",
+      "project",
+      "samples",
+      "deviceDependencies",
+      "savedSnapshotMatchesLive",
+      "completePortabilityVerified",
+      "native"
+    ],
+    "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.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds genuinely new context: what it reports (missing, ambiguous, external samples), the snapshot-vs-unsaved-edits distinction, and the platform/environment requirement for clean-state observation. These are behavioral traits the structured fields do not convey.

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?

Four tight sentences, front-loaded with the core action and followed by report scope, exclusions, and environment requirement. Each sentence carries distinct information, though the platform caveat could be tightened.

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 an output schema present, return values need not be spelled out, and the description covers the remaining gaps an agent needs: what the inspection surfaces, its limitations, and the environment precondition. Nothing required to invoke it correctly is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies operation against the current Project without introducing phantom parameters.

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 verb (Inspect) and resource (saved Live 12 sample references and file contents in the current Project), with scope clearly bounded to the saved snapshot rather than unsaved edits. It is distinguishable from write-oriented siblings, though it does not explicitly name the adjacent collect_project_media to contrast the two.

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?

Gives a clear when-not boundary ("Does not certify plug-in libraries, licenses, Max dependencies or other Sets") and a prerequisite ("Requires macOS English Live"). It lacks an explicit pointer to the alternative tool (e.g., collect_project_media) for when collection rather than inspection is wanted.

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