modularsynth-mcp

by gregorybruneau

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Undo

undo

Destructive

Revert the last change made by you or the user, cancel a scene waiting for the next bar, or stop a playing song.

Instructions

Undo the last change (yours or the user’s), like Ctrl+Z: first cancels a scene waiting for the next bar, stops a playing song.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "undo"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Nov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds meaningful behavioral detail beyond annotations: it can undo either the caller's or the user's last change, cancels a scene waiting for the next bar, and stops a playing song. It does not describe undo-stack limits or failure behavior, but the core side effects are disclosed.

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?

The description is a single front-loaded sentence with no wasted wording. It moves directly from the primary action to disambiguating scope and then to concrete side effects.

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?

For a zero-parameter undo tool with no output schema, the description contains enough information to call it correctly. Annotations already cover the mutation and destructiveness profile, and the description fills in the operational behavior an agent would need.

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?

The tool has zero parameters and schema coverage is 100%, so there are no parameter semantics for the description to clarify. The baseline score for a zero-parameter tool is appropriate.

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?

The description states a specific verb and resource: undo the last change. It further clarifies scope with "yours or the user’s," the Ctrl+Z analogy, and concrete first effects, so an agent can distinguish this from transport or scene tools without opening the schema.

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 intended use is clear: revert the most recent change. It does not explicitly name when not to use it or an alternative sibling, but no direct sibling appears to provide undo behavior, so the context is sufficient without exclusions.

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