Skip to main content
Glama
Sign In
flstudio-mcp

flstudio-mcp

by rosasynthesiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get track level (dB)

fl_get_track_level
Read-onlyIdempotent

Measure a mixer track's level by sampling meter peaks. Returns average and peak dB values during playback, or indicates when playback is stopped.

Instructions

Measure a mixer track's level by sampling meter peaks over a short window. Requires PLAYBACK -- returns playing=False (avg/peak null) when stopped/silent. {track, playing, avg_db, peak_db}.

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>"
    },
    "name": "fl_get_track_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
samplesNoReads over ~samples*100ms.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent. Description adds context: requires playback, returns playing=False when stopped, and output fields (avg, peak). No contradictions.

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?

Two sentences plus output signature. No unnecessary words. Front-loaded with verb and resource.

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?

Covers purpose, usage condition, return values. Could mention units (dB) explicitly, but 'level (dB)' in title and output field names suffice. Annotations provide safety context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (only 'samples' has description). Description does not explain 'track' parameter meaning (e.g., index base) or how 'samples' affects accuracy beyond schema's '~samples*100ms'.

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?

Explicitly states 'Measure a mixer track's level' with method 'sampling meter peaks over a short window'. Distinguishes from sibling tools like fl_analyze_audio (analysis) and fl_get_mixer_state (state).

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?

Clearly specifies 'Requires PLAYBACK' and explains behavior when stopped/silent. Implicitly guides use when playback is active. Could explicitly mention alternatives for detailed analysis.

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