PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

sound_get_inventory

Read-onlyIdempotent

Read loaded instruments and effects with their presets, drum pad maps, and Atlas knowledge to show users which sounds are available for palette planning.

Instructions

Read the pool of loaded instruments and their presets that palettes choose from.

Read-only. Returns each loaded instrument (and effects when requested) with
its preset names, current preset, drum pad map, and Atlas knowledge.
sound_plan_palette reads this inventory itself, so call it only to show
the user what is available. Atlas-only products are recommendations, not
loaded sounds.

Input Schema

TableJSON Schema

Name	Required	Description
`request`	No	Optional sound request; it decides which loaded targets and effects are relevant.
`only_used`	No	Limit mixer observations to used tracks; instruments stay included.
`preset_limit`	No	Maximum preset names read per loaded target.
`preset_start`	No	First preset index read per target.
`include_atlas`	No	Add offline Plugin Atlas knowledge to each loaded target.
`include_current`	No	Read each target's current preset.
`include_effects`	No	Include loaded effects; defaults from the request.
`include_pad_maps`	No	Read drum pad maps of loaded instruments.
`include_empty_names`	No	Keep presets with blank names.

Output Schema

TableJSON Schema

Name	Required	Default
`warnings`	No
`observed_at`	No
`locked_roles`	No
`loaded_effects`	No
`schema_version`	No	1.0
`loaded_generators`	No
`current_palette_id`	No
`session_fingerprint`	No
`known_unloaded_products`	No
`preset_discovery_coverage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: Atlas-only products are 'recommendations, not loaded sounds', preventing misinterpretation of the returned data, and notes effects are returned 'when requested'.

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 with the core purpose, then safety, then return contents, then the routing caveat. Sentences are tight and each carries information, though the 'Read-only' line partly duplicates the annotation.

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?

With an output schema covering return values and annotations covering safety, the description only needs to add routing and interpretation guidance — which it does via the sound_plan_palette note and the Atlas-vs-loaded distinction. Nothing an agent needs to call it correctly is missing.

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 all nine parameters (preset_limit, include_effects, include_atlas, etc.) are already documented in the schema. The description only loosely hints at request-driven filtering and effect inclusion, adding little beyond structured fields — baseline 3 applies.

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 and resource ('Read the pool of loaded instruments and their presets') and immediately scopes it as the pool that 'palettes choose from', distinguishing it from palette-related siblings. An agent can tell what it returns (loaded instruments, effects, preset names, current preset, drum pad map, Atlas knowledge) without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'sound_plan_palette reads this inventory itself, so call it only to show the user what is available.' This names the alternative and the exact condition for choosing this tool over it, which is the strongest form of usage guidance.

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

Deploy Server