scan_plugins
Discover which plugin commands are actually available by parsing plugin annotations and enabled state. Reports each command's arguments so you know what create_plugin_command can call.
Instructions
Discover the plugin commands this project actually has, by parsing the @command/@arg annotations in js/plugins/*.js and the enabled/disabled state in js/plugins.js. Use it to find out what create_plugin_command can call and with which args — it reports every command's key, label, description and args (name/type/default), plus whether the plugin is enabled in the editor's Plugin Manager (a disabled plugin's commands never run). create_plugin_command validates against this scan automatically, so you don't need to call this first; it's for discovery. Pass pluginName to narrow to one plugin, or enabledOnly:true to skip plugins that are installed but switched off. Read-only. NOTE: MZ has no 'required argument' annotation, so scanned args are checked for unknown names only, never for missing ones.
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": "scan_plugins"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pluginName | No | Optional: restrict to one plugin (its filename without .js) | |
| enabledOnly | No | Only report plugins enabled in js/plugins.js (default false) |