Skip to main content
Glama

undo

Revert the most recent live edit made through these VOCALOID6 tools and reload the project to restore its previous state.

Instructions

Undo the last live edit made by these tools (reloads the project). / これらのツールによる直前のライブ編集を取り消します

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important side effect: the undo triggers a project reload rather than a lightweight in-place reversal. It omits whether the undo stack is one level deep, whether redo becomes available afterward, and what happens if there is nothing to undo.

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?

Two short clauses, with the scope stated before the mechanism note, so it is front-loaded and zero-padding. The only waste is the verbatim Japanese duplication, which repeats rather than adds information for a single-language reader.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, zero-annotation tool the description covers purpose and the chief side effect (reload), but leaves the undo-stack depth, post-undo redo availability, and no-op behavior unspecified. These are the details an agent most needs before invoking a state-reverting operation.

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 takes zero parameters, so there is no parameter meaning to add; the baseline applies. Nothing in the description misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (undo) and a precisely scoped resource: the last live edit made by these tools. The parenthetical '(reloads the project)' clarifies the mechanism. It doesn't explicitly name the redo sibling as its counterpart, so differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Last live edit made by these tools' implies when it applies, but gives no explicit when-not guidance: nothing about behavior when no edit exists, whether it is single-level only, or that redo is the counterpart for reversing an undo. Usage is implied rather than directed.

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