presets_listList instrument presets with their types, including voice presets that name their voice module, so AI agents can identify available sounds in a DAW project.
List instrument presets with their type (voice presets name their voice module).
| Name | Required | Description | Default |
|---|---|---|---|
| project | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It hints at output shape (voice presets name their voice module) but says nothing about permissions, scoping, or pagination, and 'List' only weakly implies a read-only operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. It is tightly scoped, though the parenthetical adds little for such a short description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The presence of an output schema means return values need not be described, and the tool is simple (one optional param). However, the undocumented parameter and absent usage guidance leave gaps an agent would need to resolve elsewhere.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 for the undocumented 'project' parameter, but it never mentions it or explains its scoping effect. The single optional parameter is left entirely to inference.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (instrument presets), plus a clarifying note about what voice presets include. An agent can tell what it does, but there's little to distinguish it from neighbors like voices_list or sound_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this versus voices_list, instrument_show, or sound_list. There are no prerequisites or exclusion conditions, leaving the agent to infer the right context on its own.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.