PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

plugin_list_available

Lists instruments and effects in FL Studio's native Add menu on macOS, showing exact loadable names and whether each is an instrument or effect for plugin loading.

Instructions

List the instruments and effects in FL's native Add menu (macOS only).

Opens and closes the menu, which briefly changes focus; changes no project
state. Reports exact loadable names and whether each is an instrument or
an effect, for plugin_load. Menu presence is not proof of licensing or an
exhaustive install scan.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`error`	No
`source`	No	native_add_menu
`entries`	No
`platform`	Yes
`supported`	Yes
`observed_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With readOnlyHint=false, the description explains exactly why: it opens and closes the menu, briefly changing focus, while asserting no project state is changed. It further discloses that menu presence is not proof of licensing or an exhaustive scan, adding real behavioral context beyond the annotations.

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-loads the core purpose, then packs side-effect and caveat information into short clauses with no filler. Slightly dense but every sentence carries weight.

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?

An output schema exists so return format need not be restated, and the description adds the platform constraint and the important caveat that menu presence does not confirm licensing. Complete enough for a 0-param listing tool, though it could name the alternative tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies for a 0-param tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (instruments and effects in FL's native Add menu), and it is immediately distinguishable from plugin_list_loaded since this covers the available menu, not loaded plug-ins. The 'for plugin_load' clause clarifies downstream intent.

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?

The description implies usage ('for plugin_load') and adds a macOS-only scope plus a licensing caveat, but it never explicitly names the obvious alternative (plugin_list_loaded) or states when to prefer each. Usage is inferable but not spelled out.

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

Deploy Server