Skip to main content
Glama
synopsys0

PostFader V10 — FL Studio MCP Server

by synopsys0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fl_set_plugin_param_display

Destructive

Set a plug-in parameter by its displayed value (ms, dB, Hz) instead of a 0..1 guess, searching the control until readback matches your target.

Instructions

Set a plug-in parameter using the units it displays, not a 0..1 guess.

Prefer this over `fl_set_plugin_param` for anything with real units.
Normalized 0..1 has no published mapping to ms, dB or Hz, and the curve
differs per control; this searches the control until its own readback
reports the number you asked for, so no curve is ever assumed.

Address the parameter by name where it has one ("Attack"), or by
what it displays where it does not ("Auto mode"). Run
`plugins_scan_parameters` first to see both.

Controls whose display is pure text -- "Chromatic", "Low Male" -- are
enumerations with no number to search on and are refused. Use
`fl_set_plugin_param_option`, which sets them by their option text and
also reports every option the control accepts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoExplicit mixer_effect or global channel_generator target. Mutually exclusive with legacy track_index/slot_index.
parameterYesParameter index, or text matched against parameter names AND display strings (many real third-party controls have no name).
toleranceNoHow close counts. Defaults to 2% of the target, floor 0.01.
slot_indexNoLegacy zero-based effect slot 0 through 9. Supply it with track_index, or use target, never both.
target_unitNoOptional Hz, kHz, ms, seconds, dB, percent or ratio. Converts each display readback across unit prefixes. Omit for legacy first-number matching.
track_indexNoLegacy zero-based mixer index. Supply it with slot_index, or use target, never both.
allow_masterNoRequired to target mixer track 0.
target_valueYesThe number the plug-in displays: 20 for '20 ms', -18 for '-18.0 dB'. With target_unit='Hz', use 4000 for '4.0kHz'.
expected_beforeNoOptional expected normalized value and/or exact display text; refuse if any supplied field changed.
session_fingerprintNoOptional bridge/project-session fingerprint from a recent read. The write refuses after bridge reload or a reported project load. This is a concurrency guard, not authentication or a durable project identity.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv10.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already communicate a write/destructive operation. The description adds valuable behavioral nuance: it searches the control via readback until the number matches, assumes no mapping curve, and refuses pure-text enumerations. There is no contradiction with 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: purpose, preference, addressing strategy, and exclusions each get one clear block. No sentence is padding.

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 multi-parameter write tool, the combination of description, annotations, and full schema coverage covers purpose, safety, parameter identification, and the sibling to use for text-only controls. An output schema exists, so the absence of return-format detail is not a gap.

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?

With 100% schema coverage, the baseline is met by the schema. The description adds meaningful extra guidance around how to address parameters—by name when available and by display string otherwise—and clarifies target values are display-unit numbers, not normalized guesses. It leaves tolerance and guard parameters to the schema, which is reasonable.

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?

The description opens with a specific verb and resource: 'Set a plug-in parameter using the units it displays, not a 0..1 guess.' It immediately differentiates this from fl_set_plugin_param and fl_set_plugin_param_option, so an agent can tell what this tool uniquely does.

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?

It explicitly tells the agent to prefer this over fl_set_plugin_param for anything with real units, and directs pure-text enumerations to fl_set_plugin_param_option. It also instructs running plugins_scan_parameters first, giving a clear before-use workflow.

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

Deploy Server

Other Tools