Skip to main content
Glama
whatanaiceguy

kuruitsugizaki

by whatanaiceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fl_exec

Destructive

Run Python code inside FL Studio's embedded interpreter to inspect or modify the open project—channels, mixer, plugins, transport, patterns—and return the assigned result or an error traceback.

Instructions

Run Python inside the running FL's embedded interpreter, where FL's modules (channels, mixer, plugins, transport, patterns, general ...) import. For live reads or changes that need several calls or logic; one call is simpler with fl_call. Returns {ok, value} with what the code assigns to result, or {ok: false, error} with the traceback. FL's sandbox refuses files, sockets and pipes. Changes act on the open project and are not saved. Launches FL if needed. Windows with FL Studio only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outNowrite the result as JSON to this path (relative to the repo) and return only its size, for large reads; also when `result` is {'__out__': path, 'data': value}
codeYesPython source; assign the answer to `result`
timeoutNoseconds to wait for FL's answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • addedInput schema / properties / code / description
      Added value: +"Python source; assign the answer to `result`"
    • addedInput schema / properties / out / description
      Added value: +"write the result as JSON to this path (relative to the repo) and return only its size, for large reads; also when `result` is {'__out__': path, 'data': value}"
    • addedInput schema / properties / timeout / description
      Added value: +"seconds to wait for FL's answer"
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: the sandbox refuses files/sockets/pipes, changes act only on the open project and are not saved, FL may be launched on demand, and the return shape is {ok, value} or {ok: false, error} with traceback. This is substantial extra context over the destructiveHint/openWorldHint flags.

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?

Four dense sentences, front-loaded with the core action and the fl_call disambiguation early. Slightly packed with environment caveats, but each sentence carries load.

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?

No output schema exists, yet the description explains both success and failure return shapes, the `result` contract, sandbox limits, persistence behavior and platform requirements. Nothing an agent needs to invoke this 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 the schema already documents code, out and timeout. The description reinforces the `result` assignment convention and the __out__ path convention, but adds no syntax or format detail the schema lacks. 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?

Specific verb+resource: 'Run Python inside the running FL's embedded interpreter', with the module namespace (channels, mixer, plugins, transport, patterns) spelled out. It explicitly differentiates from the sibling fl_call ('one call is simpler with fl_call'), so an agent can route without opening either 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?

Gives the selecting condition ('live reads or changes that need several calls or logic') and names the alternative (fl_call) for the simpler case. It also adds environment gates: Windows with FL Studio only, and it will launch FL if needed.

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