Skip to main content
Glama
williamzujkowski

Strudel MCP Server

stop

Stop music playback in Strudel.cc to pause audio generation and live coding sessions.

Instructions

Stop playback

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition for the 'stop' tool, specifying name, description, and empty input schema.
    {
      name: 'stop',
      description: 'Stop playback',
      inputSchema: { type: 'object', properties: {} }
  • Registration of the ListToolsRequestSchema handler which returns all tools including 'stop' via getTools().
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: this.getTools()
    }));
  • Handler logic for the 'stop' tool (shared with 'pause'), delegating execution to StrudelController.stop() method.
    case 'pause':
    case 'stop':
      return await this.controller.stop();
  • Core implementation of stop functionality: sends Ctrl+. keyboard shortcut to Strudel browser page to stop playback and updates local state.
    async stop(): Promise<string> {
      if (!this._page) throw new Error('Browser not initialized. Run init tool first.');
    
      // Always use keyboard shortcut for speed
      await this._page.keyboard.press('ControlOrMeta+Period');
    
      this.isPlaying = false;
      return 'Stopped';
    }
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. 'Stop playback' implies a mutation action that halts something, but it doesn't specify effects (e.g., resets position, requires playback to be active), permissions, or side effects. This is inadequate for a tool that likely changes state.

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 extremely concise with just two words, front-loaded and waste-free. Every word earns its place by directly conveying the tool's purpose without unnecessary elaboration.

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 tool likely performs a mutation (stopping playback) with no annotations and no output schema, the description is incomplete. It doesn't explain what 'stop' entails (e.g., does it reset to start, require active playback?), return values, or error conditions, leaving significant gaps for the 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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it also doesn't compensate for any gaps since there are none. Baseline is 4 for zero parameters.

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

Purpose3/5

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

The description 'Stop playback' clearly states the action (stop) and target (playback), but it's somewhat vague about what exactly is being stopped (audio, video, music, etc.) and doesn't differentiate from sibling tools like 'pause' which might have similar functionality. It avoids tautology since it doesn't just restate the tool name.

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 like 'pause' or how it relates to other playback controls. There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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