Skip to main content
Glama
Dorico Maestro

Dorico Maestro

list_plugins

Read-onlyIdempotent

Lists VST3 plugins known to Dorico's audio engine and returns the IDs needed to load them, so you can select available instruments and effects.

Instructions

List the VST3 plugins Dorico's audio engine knows, with the id loading needs.

Returns:
    Result dictionary with ``plugins`` (name, vendor, class_id, categories) and
    the cache file they were read from.

Note:
    Read from the audio engine's VST3 cache file, not from Dorico, so a plugin
    installed after the engine last scanned is missing until Dorico restarts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhich plugins to list.instrument
nameNoPart of a plugin name to filter by.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: data comes from the audio engine's VST3 cache rather than Dorico, so plugins installed after the last scan are invisible until a Dorico restart. That staleness caveat is exactly the kind of non-obvious trait that prevents an agent misdiagnosing a 'missing' plugin.

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?

Front-loaded one-line purpose followed by clearly labeled Returns and Note sections; no filler. The Returns block partly duplicates the output schema, which is the only mild redundancy.

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?

For a two-parameter read-only lister with an output schema and full annotation coverage, this is complete: purpose, return shape, data source, and the cache-staleness limitation are all covered.

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 the kind enum and name filter are already documented in the schema. The description adds nothing about the filters and only describes the returned fields, so baseline 3 applies.

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?

States a specific verb and resource: 'List the VST3 plugins Dorico's audio engine knows', and adds the reason it matters (the id needed for loading). It is clearly a discovery/enumeration tool, though it never names the sibling (plugin_state) that an agent might confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer it calls this to discover plugin IDs before loading. There is no explicit when-to-use/when-not-to-use guidance and no mention of how it relates to plugin_state or activate_playback.

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