Skip to main content
Glama
Sign In
kuruitsugizaki

kuruitsugizaki

by whatanaiceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

profile

Idempotent

Scans a folder of FL Studio .flp files, including subfolders, to list each project's tempo, key, and arrangement length in bars, so you can choose which to open and read fully without launching FL.

Instructions

List a person's projects from a folder of their .flp files: tempo, key and arrangement length in bars, so you know which to open and read in full with project_read. Reads every .flp under the folder, subfolders included, and changes none of them; FL need not run; about 2 s for 80 projects. Also written as profile.md and profile.json to tmp/profile//. Projects that fail to read are listed, not fatal; a folder with no .flp returns {ok: false, error}. Without folder it reads config projects_folder; when that is not set, ask the user where their own projects are and pass that folder, which is then saved there, so later sessions do not ask again. When they have none, set projects_folder to 'none' with config, and profile then answers that.

Input Schema

NameRequiredDescriptionDefault
folderNothe folder of .flp projects, absolute or relative to the repo; omit to use config projects_folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • addedInput schema / properties / folder / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / folder / default
      Added value: +null
    • changedInput schema / properties / folder / description
      Previous value: -"the folder of .flp projects, absolute or relative to the repo"New value: +"the folder of .flp projects, absolute or relative to the repo; omit to use config projects_folder"
    • removedInput schema / properties / folder / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "folder"
-]
  2. Changed1 schema field changedv0.2.1
    • addedInput schema / properties / folder / description
      Added value: +"the folder of .flp projects, absolute or relative to the repo"
  3. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial context beyond annotations: reads subfolders recursively, FL need not be running, ~2s for 80 projects, writes profile.md/profile.json to tmp/profile, failed reads are listed not fatal, and the {ok: false, error} shape for an empty folder. The readOnlyHint=false annotation is consistent (the tool writes report files while changing no .flp), and the description clarifies this distinction.

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 what it does and returns before the fallback logic, and every clause carries information. It is a dense, semicolon-heavy run-on paragraph, costing a little readability, but little is wasted.

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?

With no output schema, the description fully carries the return burden: it lists per-project fields, the error shape, the on-disk artifacts, and the config resolution behavior. Nothing an agent needs to call it correctly is missing.

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% and the folder parameter is already documented, so the schema carries the base meaning. The description adds value beyond it by explaining the full default chain (config projects_folder, then ask-and-persist), which the schema only gestures at with 'omit to use config projects_folder'.

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+resource ('List a person's projects from a folder of their .flp files') and enumerates the returned fields (tempo, key, arrangement length in bars). It explicitly distinguishes itself from the sibling project_read ('which to open and read in full with project_read').

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?

Explicitly positions itself as the lightweight triage step before project_read, and gives detailed fallback guidance: omit folder to use config projects_folder, ask the user and save it when unset, and set projects_folder to 'none' when the user has none. When and when-not are both covered.

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