PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

project_get_summary

Read-onlyIdempotent

Reads the open FL Studio project's metadata, counts, dirty state, and transport status to give overall context before playback control or transport changes.

Instructions

Read the open project's metadata, counts, dirty state, and transport.

Returns the title, tempo, PPQ, mixer/channel/pattern/Playlist counts, the
undo position, dirty state, the connection with its session_fingerprint,
and the transport (playing, recording, loop mode, position, metronome,
precount, time signature). Read-only. Use it for overall context and the
transport state before transport_set; use the area list tools
(mixer_list_tracks, channel_list, pattern_list, playlist_list_tracks) for
target details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`ppq`	No
`warnings`	No
`tempo_bpm`	No
`transport`	Yes
`connection`	Yes
`dirty_flag`	No
`dirty_state`	No	unknown
`observed_at`	Yes
`channel_count`	No
`pattern_count`	No
`project_genre`	No
`project_title`	No
`project_author`	No
`schema_version`	No	1.0
`mixer_track_count`	No
`undo_history_count`	No
`playlist_track_count`	No
`undo_history_position`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' is redundant. The description's remaining content enumerates return fields, which the output schema already covers, so it adds little behavioral context beyond the structured data.

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?

Purpose and routing are front-loaded and the routing sentences earn their place, but the middle sentence enumerates the full return shape that the output schema already provides, which is mildly redundant.

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?

For a no-parameter read tool with a full output schema, the description covers purpose, routing and safety adequately; the enumerated return fields are unnecessary given the schema but do no harm.

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?

Zero parameters, so the baseline is 4; there is nothing parameter-level the description could clarify.

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 (Read) and resource (the open project's metadata, counts, dirty state, and transport), then names the sibling category it is not (the area list tools) so an agent can tell it apart from mixer_list_tracks/channel_list/pattern_list without opening a 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 explicit when-to-use ('for overall context and the transport state before transport_set') and when-not (defer to the area list tools for target details), naming concrete alternatives.

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

Deploy Server