Skip to main content
Glama
BradA1878
by BradA1878

sc_quit

Stop the audio synthesis server and release system resources when sound generation is complete.

Instructions

Quit the SuperCollider audio server and clean up resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'sc_quit' tool. Checks if the SuperCollider server is booted, quits it using scServer.quit(), resets synthDefsLoaded flag, and returns success or error message.
    case 'sc_quit': {
      if (!scServer.getBooted()) {
        return {
          content: [{ type: 'text', text: 'SuperCollider server is not running' }],
        };
      }
    
      await scServer.quit();
      synthDefsLoaded = false;
    
      return {
        content: [{ type: 'text', text: 'SuperCollider server quit successfully' }],
      };
    }
  • The tool definition including name, description, and input schema (empty object) for 'sc_quit'. This is part of the tools array returned by listTools.
    {
      name: 'sc_quit',
      description: 'Quit the SuperCollider audio server and clean up resources.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:200-202 (registration)
    Registration of the listTools handler that returns the array of all tools, including 'sc_quit'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses the main behavioral trait (quitting server and cleaning resources), but lacks details like whether this is reversible, permission requirements, or side effects on ongoing processes. It doesn't contradict any annotations.

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?

Single sentence, front-loaded with the core action, no redundant words. Every part earns its place by specifying what is quit and what additional cleanup occurs.

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 no annotations, no output schema, and a potentially destructive action (quitting a server), the description is minimally adequate. It states what happens but lacks details on return values, error conditions, or dependencies (e.g., requires server to be running).

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is fine here, but a baseline of 4 applies since it's a zero-param tool.

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 ('quit') and target resource ('the SuperCollider audio server'), plus an additional effect ('clean up resources'). It distinguishes from siblings like sc_boot (start server) and sc_status (check status).

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

Usage Guidelines4/5

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

The description implies usage context (when you want to stop the server and free resources), but doesn't explicitly state when NOT to use it (e.g., while recording/playing) or name alternatives like sc_stop_all (which stops sounds but not the server).

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