Skip to main content
Glama

plugin_presets

List a VST/AU plug-in's available presets for a Live track device or load a preset by index or name to change its sound.

Instructions

A VST/AU plug-in's preset list (as the plug-in exposes it to Live), or select one by index or name (exact, else first containing the text).

Parameters:

  • track_index / device_index: The plug-in

  • preset_index / preset_name: Preset to load (omit both to list)

  • track_type: "track", "return" or "master"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "device_index": "<device_index>"
    },
    "name": "plugin_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_typeNotrack
preset_nameNo
track_indexYes
device_indexYes
preset_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a genuinely useful trait: the preset list is whatever the plug-in exposes to Live, and name lookup falls back to substring matching when an exact match fails. It does not say what happens when nothing matches, whether loading a preset mutates device state or is undoable, or whether indices are zero-based, leaving real gaps for a state-changing operation.

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 two-mode summary is front-loaded, followed by a compact bulleted parameter list with no filler sentences. Every line carries information. Minor deduction for the dangling first sentence, which lacks a main verb and reads as an incomplete clause.

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

Completeness3/5

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

An output schema exists, so return values need not be explained here. For a five-parameter, state-affecting tool with zero annotation coverage, the remaining gaps matter: no indication of failure behavior on an unmatched name or out-of-range index, and no note on whether selection persists in the Live set. It is adequate to attempt a call but not to predict or recover from edge cases.

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 description coverage is 0%, so the description must compensate, and it does: all five parameters are addressed, including the valid values for track_type ('track', 'return', 'master') that the schema leaves as an unconstrained string with only a default. The matching semantics for preset_name add real meaning. The track_index/device_index explanation ('The plug-in') is thin — no indexing base or how to discover valid indices.

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 names the concrete resource (a VST/AU plug-in's preset list as exposed to Live) and the two operations (list, or select by index/name). The list mode is expressed as a noun phrase rather than a verb ('A VST/AU plug-in's preset list'), so it reads slightly fragmentary, but an agent can still tell exactly what the tool touches. No sibling differentiation is offered, which keeps it below 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 gives an explicit mode-selection rule: 'preset_index / preset_name: Preset to load (omit both to list)', which tells the agent precisely how to get listing behavior versus loading behavior. Matching behavior is also specified (exact first, else first containing the text). It stops short of naming when to use a different tool (e.g., a device-inventory or device-knowledge sibling) or any preconditions.

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