Skip to main content
Glama

inspect_preset_file

Read-onlyIdempotent

Read a .adg or .adv preset file to list its device, rack macro names, chains or Drum Rack pads with notes, and nested devices without loading it in Ableton Live.

Instructions

What a preset file holds, without loading it and without Live: the device, a rack's visible macro names, its chains (or Drum Rack pads with their notes) and the devices in each, nested racks included.

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": {
      "path": "<path>"
    },
    "name": "inspect_preset_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesA .adg or .adv file in the User Library, a pack or the Core Library, e.g. ~/Music/Ableton/User Library/Presets/Example.adg

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint:false and openWorldHint:false, so the safety profile is covered. The description adds useful behavior beyond that: no loading side effect, no Live dependency, and recursion into nested racks. It says nothing about failure modes (non-.adg/.adv files, missing files), output format, or size/depth limits, which keeps it at a solid middle score.

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?

One dense sentence with zero filler, and the payoff ('what a preset file holds') is front-loaded ahead of the qualifiers and the enumerated contents. The mid-sentence line break and the parenthetical '(or Drum Rack pads with their notes)' add mild parsing friction but no wasted words.

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 one-parameter, read-only, closed-world tool with full annotation coverage, the description covers the essential gaps: what is returned, that nothing is loaded, and that nesting is traversed. With no output schema present, the enumeration of returned content is valuable; only the actual shape of the response and error behavior remain unstated.

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?

There is a single required parameter with 100% schema description coverage, including accepted file types and an example path, so the schema already does the work. The description adds no path semantics (no validation rules, no relative-vs-absolute behavior, no permission notes), so this sits at the baseline.

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 resource precisely (a preset file) and enumerates exactly what it returns: device, visible macro names of a rack, chains or Drum Rack pads with their notes, and nested devices. It also implicitly separates itself from load_device and any Live-dependent sibling by stating it works 'without loading it and without Live'. The only shortfall is that the action verb is expressed as 'What a preset file holds' rather than a direct verb, though the meaning is unambiguous.

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?

Clear usage context is given: use this when you want preset contents without loading the preset and without a running Live instance, which is a genuine selection signal against siblings such as load_device or live_api. There is no explicit when-not-to-use clause or named alternative, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.