Skip to main content
Glama
cavi-ai

ableton-mcp

by cavi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_presets

Read-onlyIdempotent

Search local NKS presets by name, tags, product, or favorite status; filter unavailable inventory and distinguish missing configuration from no matches.

Instructions

Search optional local NKS presets by name, across products unless productSlug is given. Missing inventory records are excluded. Result catalog.configured distinguishes unavailable configuration from no matches.

Input Schema

NameRequiredDescriptionDefault
tagsNoRequire every supplied tag.
limitNoMaximum returned presets; defaults to 50 and is capped at 200.
queryNoName query.
favoriteNoReturn only favorites or non-favorites.
productSlugNoProduct slug.

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": {
+      "catalog": {
+        "properties": {
+          "configured": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "configured"
+        ],
+        "type": "object"
+      },
+      "presets": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "presets",
+      "catalog"
+    ],
+    "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
    • addedInput schema / properties / limit / description
      Added value: +"Maximum returned presets; defaults to 50 and is capped at 200."
    • removedInput schema / required
      Removed value: -[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety burden is lifted. The description still adds genuine behavioral context: exclusion of missing inventory records, and the fact that catalog.configured disambiguates 'unavailable configuration' from 'no matches' — an important distinction an agent would otherwise misread as an empty result.

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?

Three sentences, the scoping rule front-loaded ahead of the filtering and result caveats, with no filler. The word 'optional' in the opening clause is the only unclear element and keeps it from a 5.

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?

For a five-parameter, no-required-parameter search tool with a full output schema, the description covers scope, filtering exclusions, and the one result field that needs interpretation. Return-value shape is rightly left to the output schema; only minor details like pagination semantics via limit are omitted, which the schema handles.

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 baseline is 3, but the description adds real meaning: productSlug's presence vs absence changes search scope from one product to all, and 'by name' ties the query parameter to name matching. That is useful semantics beyond the one-line schema descriptions.

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 ('Search ... NKS presets') and bounds the domain to 'local NKS presets', which separates it from siblings like search_browser_items, search_local_splice_samples, and get_preset. The qualifier 'optional' is ambiguous and slightly muddies the scope, and it never names a sibling outright, so it falls just short of a 5.

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?

It states the scoping rule clearly: search runs 'across products unless productSlug is given', which tells the agent when to supply that parameter. It also notes that missing inventory records are excluded. However, it names no alternative tool or when-not-to-use condition, so it is clear context without explicit routing.

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