Skip to main content
Glama
BradA1878
by BradA1878

sc_record_stop

Stop audio recording in SuperCollider MCP Server to complete sound capture sessions initiated through natural language commands.

Instructions

Stop recording audio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for sc_record_stop tool: checks if server is booted, executes SuperCollider code to stop recording, returns success message.
    case 'sc_record_stop': {
      if (!scServer.getBooted()) {
        return {
          content: [{ type: 'text', text: 'Error: SuperCollider server is not running.' }],
          isError: true,
        };
      }
    
      await scServer.executeCode('Server.default.stopRecording;');
    
      return {
        content: [{ type: 'text', text: 'Recording stopped' }],
      };
    }
  • src/index.ts:181-188 (registration)
    Tool registration in the tools array, including name, description, and empty input schema (no parameters required).
    {
      name: 'sc_record_stop',
      description: 'Stop recording audio',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for sc_record_stop: accepts an empty object (no arguments).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Stop recording audio' indicates a mutation operation (stopping), but doesn't disclose behavioral traits such as whether this requires specific permissions, what happens to the recorded audio (e.g., saved, discarded), error conditions, or side effects. It's minimal and leaves critical behavior unspecified for a mutation tool.

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 ('Stop recording audio') with zero waste. It's front-loaded and appropriately sized for a simple tool with no parameters, making it easy to parse quickly.

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's complexity (mutation with no parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or behavioral details like whether it stops a specific recording or all recordings. For a mutation tool, this leaves significant gaps in understanding.

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 schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as there's nothing to compensate for.

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 'Stop recording audio' clearly states the action (stop) and resource (recording audio), making the tool's purpose immediately understandable. It distinguishes from siblings like 'sc_record_start' (start recording) and 'sc_stop_all' (stop all operations). However, it doesn't specify what exactly gets stopped (e.g., a specific recording session vs. all recordings), which prevents a perfect 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 when recording needs to be stopped, but provides no explicit guidance on when to use this tool versus alternatives like 'sc_stop_all'. It doesn't mention prerequisites (e.g., requires an active recording session) or exclusions. The context is somewhat clear from the tool name and sibling tools, but lacks explicit instructions.

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