Skip to main content
Glama
whatanaiceguy

kuruitsugizaki

by whatanaiceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

project_read

Read-onlyIdempotent

Read an FL Studio .flp file into JSON without running FL or altering it, so you can inspect project contents, extract parts, or verify writes.

Instructions

Read one FL Studio .flp file into JSON; FL need not run and the file is not changed. Use it to see what a project holds, to take parts from it, or to check what project_write wrote. For the style across many projects use profile; for the project open in FL right now, fl_exec. Views: 'summary' (start here: instruments, per-pattern stats, a per-track arrangement timeline, mixer effects); 'compact' (default: every note and clip as rows, the same shape project_write accepts; notes [bar, beat, tick, len_ticks, key, vel, instrument#], clips [track, bar, beat, tick, len_ticks, src, trim?] where src is a pattern id, s a sample, a an automation clip); 'full' (exact, round-trips byte for byte; large). Fails with the parser's error on a file that is not an .flp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesthe .flp file, absolute or relative to the repo
viewNo'compact', 'summary' or 'full'compact
unusedNoalso list patterns not placed in the playlist and parked clips
patternsNoonly these pattern ids (compact and full)
arrangementsNoonly these arrangements, by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.1
    • addedInput schema / properties / arrangements / description
      Added value: +"only these arrangements, by name"
    • addedInput schema / properties / path / description
      Added value: +"the .flp file, absolute or relative to the repo"
    • addedInput schema / properties / patterns / description
      Added value: +"only these pattern ids (compact and full)"
    • addedInput schema / properties / unused / description
      Added value: +"also list patterns not placed in the playlist and parked clips"
    • addedInput schema / properties / view / description
      Added value: +"'compact', 'summary' or 'full'"
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety baseline is covered. The description adds genuinely useful context beyond that: FL need not be running, the file is not changed, and the failure mode (parser error on a non-.flp). It stops short of describing pagination or cost of the 'large' full view in more detail, so a 4 rather than a 5.

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?

Front-loaded with purpose and the routing sentence before the detailed view breakdown, and every sentence carries information. The dense view/row-format sentence is long but earns its place; nothing is redundant boilerplate.

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?

Though there is no output schema, the description spells out the three view shapes and the exact field layout of the default return, plus error behavior — everything an agent needs to interpret results and call correctly is present for a 5-parameter 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?

Schema coverage is 100%, so the baseline is 3, but the description substantially enriches meaning beyond the terse schema: it defines what each view returns ('summary' contents, 'compact' row shape, 'full' byte-for-byte round-trip) and the notes/clips row layout including the src encoding (pattern id, s<N> sample, a<N> automation). It never mentions the 'unused', 'patterns', or 'arrangements' parameters, leaving that to the schema.

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 and resource ('Read one FL Studio .flp file into JSON') and immediately distinguishes itself from siblings by naming project_write (whose output it verifies), profile, and fl_exec. An agent can tell exactly what this does versus the other 12 tools without opening any 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 use cases ('see what a project holds, to take parts from it, or to check what project_write wrote') and routes alternatives by condition: profile for style across many projects, fl_exec for the project open in FL right now. This is textbook when-to-use/when-not coverage.

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