Skip to main content
Glama
Sign In
flstudio-mcp

flstudio-mcp

by rosasynthesiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set plugin parameter

fl_plugin_set_param
Idempotent

Set any plugin parameter by name or index to a normalized value between 0 and 1, and undo the adjustment if needed.

Instructions

Set one plugin parameter (normalised 0..1). param may be an index or a name; names are resolved from the live param list. The change is logged and undo-able via fl_rollback_last_change. Returns before/after plus the resolved {index, name}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track": "<track>",
      "slot": "<slot>",
      "param": "<param>",
      "value": "<value>"
    },
    "name": "fl_plugin_set_param"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
slotYes
paramYesParam index (int) or name (str, e.g. 'Decay time').
valueYesNormalised 0..1.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The description reveals that the operation is logged and undo-able, and that it returns before/after values plus resolved index/name. This adds behavioral context beyond the annotations (idempotentHint=true, destructiveHint=false), which already indicate safety. No contradiction with 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 three sentences, well-structured, and front-loaded with the core purpose. Each sentence adds essential information without redundancy.

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?

Given the tool has 4 required parameters and an output schema, the description covers the core functionality, param resolution, undoability, and return values. It does not detail the output schema format, but that is expected to be in the schema itself. The description is sufficiently complete for a single-parameter setter.

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 schema description coverage is 50% (only 'param' and 'value' have descriptions). The description clarifies that 'param' can be an index or name resolved from the live list, adding value. For 'value', it restates the normalized range already in the schema. It does not cover 'track' or 'slot', but the overall explanation partially compensates for low coverage.

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 clearly states 'Set one plugin parameter' and specifies the normalization range, param resolution, and undoability. It distinguishes this tool from siblings like fl_plugin_get_params (which retrieves parameters) and fl_rollback_last_change (which undoes changes).

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

Usage Guidelines4/5

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

The description mentions that changes are undo-able via fl_rollback_last_change, giving a clear alternative for reversal. It implicitly indicates when to use this tool (to set a single parameter) but does not explicitly state when not to use it or compare with other set tools like fl_set_mixer_volume.

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