Skip to main content
Glama
williamzujkowski

Strudel MCP Server

redo

Reverses the last undo action to restore previous changes in Strudel.cc music patterns during live coding sessions.

Instructions

Redo action

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'redo' tool. Pops the last state from redoStack, pushes current pattern to undoStack, writes the redo pattern to the controller, and returns success or 'Nothing to redo'.
    case 'redo':
      if (!this.isInitialized) {
        return 'Browser not initialized. Run init first.';
      }
      if (this.redoStack.length > 0) {
        const currentRedo = await this.controller.getCurrentPattern();
        this.undoStack.push(currentRedo);
        // Enforce bounds to prevent memory leaks
        if (this.undoStack.length > this.MAX_HISTORY) {
          this.undoStack.shift();
        }
        const next = this.redoStack.pop()!;
        await this.controller.writePattern(next);
        return 'Redone';
      }
      return 'Nothing to redo';
  • Registration of the 'redo' tool in the getTools() method, which is used by the ListToolsRequestSchema handler to expose available tools.
    {
      name: 'redo',
      description: 'Redo action',
      inputSchema: { type: 'object', properties: {} }
    },
  • Input schema for the 'redo' tool: no parameters required.
    inputSchema: { type: 'object', properties: {} }
  • Declaration of undoStack and redoStack arrays used by undo/redo functionality.
    private undoStack: string[] = [];
    private redoStack: string[] = [];
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. 'Redo action' doesn't indicate whether this is a read or write operation, what gets modified, whether it requires specific state conditions, or what the expected outcome is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While extremely brief at just two words, this isn't true conciseness but rather under-specification. The description is front-loaded but fails to provide meaningful information, making the brevity unhelpful rather than efficient.

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

Completeness1/5

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

For a tool with no annotations, no output schema, and a sibling 'undo' tool, the description is completely inadequate. It doesn't explain what 'redo' means in this context, what gets redone, or how this differs from 'undo' - leaving critical gaps for agent understanding.

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 with 100% schema coverage, so the baseline is 4. The description doesn't need to explain parameters, and it appropriately doesn't attempt to describe non-existent parameters.

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

Purpose2/5

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

The description 'Redo action' is a tautology that merely restates the tool name without specifying what action is being redone or what resource is involved. It doesn't distinguish this tool from its sibling 'undo' or other history-related tools, providing only vague purpose information.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance about when to use this tool versus alternatives. There's no mention of prerequisites, context, or relationship to the 'undo' sibling tool, leaving the agent with no usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/williamzujkowski/strudel-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server