Skip to main content
Glama
BradA1878
by BradA1878

sc_boot

Start the SuperCollider audio server to enable sound synthesis. Required before generating any audio through the MCP server.

Instructions

Boot the SuperCollider audio server. Must be called before any sound synthesis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'sc_boot' tool. It checks if the SuperCollider server is already booted, boots it if not using scServer.boot(), sets synthDefsLoaded to true, and returns a success message.
    case 'sc_boot': {
      if (scServer.getBooted()) {
        return {
          content: [{ type: 'text', text: 'SuperCollider server is already running' }],
        };
      }
    
      await scServer.boot();
    
      // Mark as loaded - we'll use inline synths instead of pre-loaded SynthDefs
      synthDefsLoaded = true;
    
      return {
        content: [
          {
            type: 'text',
            text: 'SuperCollider server booted successfully. All synth definitions loaded.',
          },
        ],
      };
    }
  • src/index.ts:44-51 (registration)
    Registration of the 'sc_boot' tool in the MCP tools list, including its name, description, and input schema (no parameters required).
    {
      name: 'sc_boot',
      description: 'Boot the SuperCollider audio server. Must be called before any sound synthesis.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the 'sc_boot' tool, defining an empty object (no input 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 states the tool boots the server and that this is required before synthesis, which covers the essential behavior. However, it doesn't mention potential side effects, error conditions, or what 'booting' entails technically (e.g., startup time, resource allocation).

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 perfectly concise with two sentences that each earn their place: the first states the core action, the second provides critical usage guidance. There's zero wasted text, and the information is front-loaded with the essential purpose.

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

Completeness4/5

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

Given the tool's simplicity (no parameters, no output schema) and the clear sibling context, the description is nearly complete. It explains what the tool does and when to use it. The main gap is lack of information about what happens after booting completes or potential failure modes, but for a zero-parameter initialization tool, this is reasonably complete.

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 description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and usage context.

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 ('Boot') and target resource ('SuperCollider audio server'), distinguishing it from siblings like sc_status or sc_quit. It explicitly defines the tool's purpose as starting the audio server, which is distinct from execution or playback tools.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Must be called before any sound synthesis.' This clearly indicates it's a prerequisite for other audio-related operations and distinguishes it from alternatives like sc_execute or sc_play_synth that would fail without the server being booted first.

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