fl-studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fl_statusA | Check the live FL bridge, version, current selection, recording state and capabilities. |
| list_fl_tracksA | List track names and indices; channel results also show mixer routing. Follow next_start. |
| list_fl_pluginsA | Discover loaded effects on a mixer track, or the instrument at a global channel index. |
| get_fl_parametersB | Read parameter names, normalized values, display units and short-lived edit handles. Follow next_start. |
| set_fl_parameterA | Change one freshly inspected knob and return actual readback. Refuses stale values and recording; stores bridge undo. |
| undo_fl_changeA | Restore the latest bridge knob change, provided the plugin and value still match. Does not invoke FL's global undo. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: status inspection, track listing, plugin listing, parameter reading, parameter writing, and undo. The boundary between inspecting a plugin and reading its parameters is clear from the descriptions.
All tool names follow a consistent snake_case verb_fl_noun pattern. The verbs are used predictably: get for reads, list for collections, set for mutation, and undo for reversal.
Six tools are well-scoped for an FL Studio bridge focused on safely inspecting and editing parameters. Each tool has a clear role and no obvious redundancy.
The parameter-editing lifecycle is covered: check status, discover tracks and plugins, read parameters, set a parameter, and undo a change. Minor gaps exist around broader FL Studio control such as transport actions, plugin loading, or redo.