Skip to main content
Glama
BradA1878
by BradA1878

sc_stop_all

Stop all currently playing audio synthesis immediately to manage server lifecycle and control real-time sound generation.

Instructions

Stop all currently playing synths immediately

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'sc_stop_all' tool. It checks if the SuperCollider server is booted and, if so, executes the SuperCollider command 'Server.default.freeAll;' to free all synths, stopping all sounds.
    case 'sc_stop_all': {
      if (!scServer.getBooted()) {
        return {
          content: [{ type: 'text', text: 'Error: SuperCollider server is not running.' }],
          isError: true,
        };
      }
    
      await scServer.executeCode('Server.default.freeAll;');
    
      return {
        content: [{ type: 'text', text: 'All synths stopped' }],
      };
    }
  • The tool schema definition for 'sc_stop_all', including name, description, and empty input schema (no parameters required). This is part of the tools array used for tool listing and validation.
    {
      name: 'sc_stop_all',
      description: 'Stop all currently playing synths immediately',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:200-202 (registration)
    Registration of all tools, including 'sc_stop_all', via the ListToolsRequestSchema handler that returns the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
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 the action ('stop all... immediately') which implies a destructive/mutative operation, but doesn't clarify side effects (e.g., whether audio cuts abruptly, if resources are freed, or if this affects scheduled synths). It lacks details on error conditions or response behavior, leaving gaps for a tool with potential impact.

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, direct sentence with zero wasted words. It front-loads the core action ('Stop all currently playing synths') and adds a critical modifier ('immediately') efficiently. Every element serves a clear purpose, making it highly concise and well-structured.

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 complexity (simple, parameterless action) and lack of annotations/output schema, the description is minimally adequate. It states what the tool does but omits behavioral nuances (e.g., what 'immediately' entails operationally, success/error responses). For a destructive tool with no structured safety hints, it should ideally include more context about effects and limitations.

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 absence of inputs. The description adds no parameter-specific information, which is appropriate here. A baseline of 4 is applied as it compensates adequately for the simple parameterless case without redundancy.

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

Purpose5/5

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

The description clearly states the specific action ('stop all currently playing synths') and the manner ('immediately'), distinguishing it from siblings like sc_quit (shutdown) or sc_record_stop (recording). It uses a precise verb+resource combination that leaves no ambiguity about its function.

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 when synths are playing and immediate cessation is needed, but provides no explicit guidance on when to use this versus alternatives like sc_quit or sc_stop (if existed). It doesn't mention prerequisites (e.g., requires synths to be active) or exclusions, leaving usage context partially inferred.

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/BradA1878/mcp-wave'

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