Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browse_local_splice_directory

Read-onlyIdempotent

Page through local Splice folders and audio files, optionally including MCP tags and favorites. Search returned paths individually when a broad query is truncated.

Instructions

Page through immediate subfolders and audio files inside a configured local Splice root. Optionally join private MCP tags and favorites for audio files. Returned folder paths can be searched individually when a broad search is truncated. Skips symlinks and non-audio files; not Splice cloud browsing, downloads, or license verification.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries per page; defaults to 100.
offsetNoZero-based entry offset; defaults to zero.
rootPathYesAbsolute configured Splice root or descendant folder returned by this tool.
includeMetadataNoInclude private MCP tags and favorites for audio-file entries.

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": {
+      "entries": {
+        "items": {
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "sourcePath": {
+              "type": "string"
+            },
+            "type": {
+              "enum": [
+                "directory",
+                "audio_file"
+              ]
+            }
+          },
+          "required": [
+            "name",
+            "type",
+            "sourcePath"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "nextOffset": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "offset": {
+        "type": "integer"
+      },
+      "rootPath": {
+        "type": "string"
+      },
+      "scope": {
+        "const": "local_files_only"
+      },
+      "total": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "rootPath",
+      "scope",
+      "offset",
+      "total",
+      "nextOffset",
+      "entries"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. Addedv0.2.0

TDQS

A4.3/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, so the description is free to add filtering semantics the annotations cannot express: symlinks and non-audio files are skipped, and metadata (tags/favorites) is only joined on request. This is meaningful behavioral context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the core enumeration behavior, then the metadata option, then the paging handoff, then the exclusions. No filler and every clause carries distinct information.

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 and 100% schema coverage, the description only needs to cover behavior: paging, optional metadata join, filtering rules, and scope exclusions. All of these are present, leaving nothing an agent needs missing.

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 limit, offset, rootPath, and includeMetadata are all documented in the schema already. The description only restates the metadata join and the paging concept without adding format or constraint detail, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Page through') and resource ('immediate subfolders and audio files inside a configured local Splice root'), and explicitly scopes itself against related capabilities ('not Splice cloud browsing, downloads, or license verification'). An agent can separate this from list_local_splice_roots and search_local_splice_samples without opening a schema.

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 clear operative context: use it to enumerate a root, and 'returned folder paths can be searched individually when a broad search is truncated' implies the handoff to a search tool. Explicit exclusions are stated. However, it never names the sibling tool to switch to, so the routing is inferred rather than spelled out.

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