modularsynth-mcp

Overview Schema Source Related Servers Discussions Admin

Save scene

save_scene

Destructive

Saves all module settings and sequences as a named scene or overwrites an existing scene, returning the scene ID for recalling intros, verses, choruses, or breaks; tempo and clock state are excluded.

Instructions

Save the current settings and sequences of every module as a scene (like a snapshot: intro, verse, chorus, break…), or overwrite an existing scene. Up to 16 scenes. Tempo and the clock's run state are not part of scenes. Returns the scene id.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`scene`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Nov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag this as a non-read-only, destructive write; the description earns extra credit by disclosing the 16-scene ceiling, that overwriting replaces an existing scene, that transport state is intentionally excluded, and that an id is returned. It does not say what happens when the 16-scene limit is already reached.

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?

Three short sentences, front-loaded with the core action, followed by the limit and the exclusions, then the return value. Nothing is redundant.

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?

For a destructive write tool with no output schema, the description covers limits, exclusions, overwrite semantics, and return value. The only material gap is the ambiguous relationship between the 'name' and 'scene' parameters, which an agent would have to guess at.

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 description coverage is 0%, so the description must carry the parameter burden, and it never maps the two schema keys to behavior: it is unclear whether 'name' identifies the new scene, whether 'scene' is the id of the scene to overwrite, or how the two interact. The overwrite concept is mentioned but not tied to any parameter.

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 ('Save ... as a scene') plus the overwrite variant, and explains what a scene is with a concrete analogy (intro, verse, chorus, break) so an agent unfamiliar with the domain can tell it apart from recall_scene, set_song, or set_transport.

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?

The two operating modes (create a new scene vs. overwrite an existing one) are stated, and the description rules out tempo and the clock's run state as out of scope, which prevents a common mis-invocation. It stops short of naming the counterpart tool (recall_scene) for the load direction.

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