PostFader V12 — FL Studio MCP Server

Overview Schema Source Related Servers Discussions Admin

channel_list

Read-onlyIdempotent

List all Channel Rack channels with mix, routing, and generator details. Returns global indices and fingerprints for channel_set, step editing, and plug-in targets.

Instructions

List every Channel Rack channel with its mix, routing, and generator.

Read-only. Each channel has a global channel_index, name, color, volume,
pan, pitch, mute/solo/selection, mixer destination, generator identity, and
a channel_fingerprint. Use the index for channel_set, channel_get_steps,
piano_roll tools, and channel_generator plug-in targets; pass the
fingerprint as channel_set's expected_before guard.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`partial`	No
`channels`	Yes
`warnings`	No
`observed_at`	Yes
`schema_version`	No	1.0
`observation_atomic`	No
`project_dirty_flag`	No
`total_channel_count`	Yes
`scanned_channel_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv11.0.2Oct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description's 'Read-only.' is largely redundant. It does add useful behavioral context beyond annotations: the full set of returned attributes and the channel_fingerprint's role as an optimistic-concurrency guard for channel_set.

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?

Purpose is front-loaded in one sentence, followed by a compact field inventory and a single sentence of cross-tool usage guidance. The only mild waste is restating 'Read-only' that the annotations already declare.

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?

An output schema exists, so the description need not enumerate return fields, yet the enumeration and the index/fingerprint guidance give the agent everything needed to chain into channel_set, channel_get_steps, and piano_roll. No missing precondition or failure-mode information of significance for a zero-arg read tool.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. It correctly adds no spurious parameter discussion.

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 first sentence gives a specific verb (List) and resource (every Channel Rack channel) plus the scope of data returned (mix, routing, generator). It is clearly distinguishable from siblings like channel_get_steps, mixer_list_tracks, or pattern_list, which cover different resources.

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

Usage Guidelines3/5

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

The description tells the agent what to do with the returned index and fingerprint (feed them to channel_set, channel_get_steps, piano_roll, plug-in targets), which implies this is the read step preceding those calls. However, it never explicitly states when to call this tool versus alternatives, and no exclusions or preconditions are given.

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

Deploy Server