Skip to main content
Glama
williamzujkowski

Strudel MCP Server

show_errors

Display captured console errors and warnings to identify and resolve issues in Strudel music generation and live coding sessions.

Instructions

Display captured console errors and warnings from Strudel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'show_errors' tool: retrieves console errors and warnings from StrudelController and formats them for display.
    case 'show_errors':
      const errors = this.controller.getConsoleErrors();
      const warnings = this.controller.getConsoleWarnings();
    
      if (errors.length === 0 && warnings.length === 0) {
        return 'No errors or warnings captured.';
      }
    
      let result = '';
      if (errors.length > 0) {
        result += `❌ Errors (${errors.length}):\n${errors.map(e => `  • ${e}`).join('\n')}\n`;
      }
      if (warnings.length > 0) {
        result += `⚠️ Warnings (${warnings.length}):\n${warnings.map(w => `  • ${w}`).join('\n')}`;
      }
      return result.trim();
  • Tool registration including name, description, and empty input schema (no parameters required).
    {
      name: 'show_errors',
      description: 'Display captured console errors and warnings from Strudel',
      inputSchema: { type: 'object', properties: {} }
    },
  • Input schema for show_errors tool: accepts no parameters.
    inputSchema: { type: 'object', properties: {} }
  • Helper method returning a copy of captured console errors array.
    getConsoleErrors(): string[] {
      return [...this.consoleErrors];
    }
  • Helper method returning a copy of captured console warnings array.
    getConsoleWarnings(): string[] {
      return [...this.consoleWarnings];
    }
  • Sets up Playwright page event listeners to capture console errors and warnings, populating the arrays used by getConsoleErrors/Warnings. Called during initialize().
    private setupConsoleMonitoring(): void {
      if (!this._page) return;
    
      this._page.on('console', (msg) => {
        const type = msg.type();
        const text = msg.text();
    
        if (type === 'error') {
          this.consoleErrors.push(text);
          this.logger.error('Strudel console error:', text);
        } else if (type === 'warning') {
          this.consoleWarnings.push(text);
          this.logger.warn('Strudel console warning:', text);
        }
      });
    
      this._page.on('pageerror', (error) => {
        this.consoleErrors.push(error.message);
        this.logger.error('Strudel page error:', error.message);
      });
    }
Behavior2/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. It states what the tool does but doesn't describe how it behaves—e.g., whether it shows real-time errors, historical logs, requires specific conditions to have errors captured, or what the output format looks like. This is inadequate for a tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the complexity of error reporting and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'captured' means, how errors are collected, the format of the display, or any behavioral aspects, leaving significant gaps for the agent to understand the tool's 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 has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly implies no parameters are required, aligning with the schema. A baseline of 4 is appropriate as it doesn't contradict the schema.

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?

The description clearly states the action ('Display') and the resource ('captured console errors and warnings from Strudel'), providing a specific verb+resource combination. However, it doesn't distinguish itself from sibling tools like 'diagnostics' or 'performance_report' which might also involve error reporting, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., after running diagnostics), exclusions, or how it differs from siblings like 'diagnostics' or 'performance_report', leaving the agent to infer usage context.

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