Skip to main content
Glama
williamzujkowski

Strudel MCP Server

status

Check current browser and playback status for Strudel music patterns to monitor live coding sessions and audio generation.

Instructions

Get current browser and playback status (quick state check)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'status' MCP tool in the getTools() method with name, description, and empty input schema.
    {
      name: 'status',
      description: 'Get current browser and playback status (quick state check)',
      inputSchema: { type: 'object', properties: {} }
    },
  • The executeTool switch case handler for 'status' which delegates to StrudelController.getStatus().
    case 'status':
      return this.controller.getStatus();
  • Core implementation of getStatus() in StrudelController that returns the browser and playback status object.
    getStatus(): {
      initialized: boolean;
      playing: boolean;
      patternLength: number;
      cacheValid: boolean;
      errorCount: number;
      warningCount: number;
    } {
      return {
        initialized: this._page !== null,
        playing: this.isPlaying,
        patternLength: this.editorCache.length,
        cacheValid: this.editorCache.length > 0 && (Date.now() - this.cacheTimestamp) < this.CACHE_TTL,
        errorCount: this.consoleErrors.length,
        warningCount: this.consoleWarnings.length
      };
    }
  • Input schema for the 'status' tool: empty object (no parameters).
    inputSchema: { type: 'object', properties: {} }
Behavior3/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 indicates this is a read operation ('Get') and implies it's non-destructive and quick, but it doesn't detail aspects like response format, potential errors, or performance characteristics. This is adequate for a simple tool but lacks depth for richer context.

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 front-loads the core purpose ('Get current browser and playback status') and adds useful context ('quick state check') without any wasted words. It's appropriately sized for a simple tool and structured to convey key information immediately.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is complete enough to understand its basic function. However, it could be more comprehensive by specifying what 'status' includes or how it differs from other status-related tools, which would enhance contextual understanding for an AI agent.

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, and the input schema has 100% description coverage, so there are no parameters to document. The description doesn't need to add parameter information, and it appropriately focuses on the tool's purpose without unnecessary details, earning a high baseline score for this dimension.

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 tool's purpose with a specific verb ('Get') and resource ('current browser and playback status'), making it easy to understand what the tool does. However, it doesn't explicitly distinguish this status check from other sibling tools like 'diagnostics' or 'performance_report', which might also provide status-related information, 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 Guidelines3/5

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

The description implies usage context by mentioning 'quick state check', suggesting it's for fast status retrieval rather than detailed analysis. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'diagnostics' or 'performance_report', nor does it specify any exclusions or prerequisites, leaving some ambiguity.

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