Retrieves an overview of the open project—name, unsaved changes, sample rate, track/scene/return-bus counts, and audio-engine status—so you can orient before acting.
Overview of the open project: name, unsaved changes, sample rate, number of tracks, scenes and return buses, and whether the audio engine runs. Call this first to orient yourself.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.0Does 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 elsewhere. The description adds real value by disclosing the exact payload of the call (unsaved-changes flag, engine-running flag), which is the only signal about what comes back since there is no output schema. It does not cover failure modes such as calling with no project open.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler, and the informative field enumeration is front-loaded before the call-to-action. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, no output schema, and full annotation coverage of safety semantics, the description supplies the one missing element: the contents of the response. An agent has everything it needs to decide to call this tool and interpret the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, which is the baseline-4 case. Nothing in the description misleads about inputs, and the empty schema makes the parameter story unambiguous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource ('the open project') and enumerates exactly what the overview contains: name, unsaved changes, sample rate, track/scene/return-bus counts, engine status. That is well beyond a restated name. It does not explicitly contrast with the nearest sibling (session_save) or with tracks_list/scenes_list, so it falls just short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Call this first to orient yourself' gives explicit ordering guidance that no sibling provides, telling the agent where in a workflow this belongs. It does not name when-not to call it or point to a specific alternative, so there's no full exclusion logic.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.