Skip to main content
Glama
BradA1878
by BradA1878

sc_record_start

Start recording audio output to a specified file for saving synthesized sounds from the SuperCollider server.

Instructions

Start recording audio output to a file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesOutput filename (will be saved in recordings/ directory)

Implementation Reference

  • The handler case for 'sc_record_start' tool. It validates the filename input using Zod, checks if the SuperCollider server is booted, generates SuperCollider code to start recording to 'recordings/{filename}', executes it via scServer, and returns a success message.
    case 'sc_record_start': {
      const schema = z.object({ filename: z.string() });
      const { filename } = schema.parse(args);
    
      if (!scServer.getBooted()) {
        return {
          content: [{ type: 'text', text: 'Error: SuperCollider server is not running. Call sc_boot first.' }],
          isError: true,
        };
      }
    
      const code = `Server.default.record("recordings/${filename}");`;
      await scServer.executeCode(code);
    
      return {
        content: [{ type: 'text', text: `Started recording to recordings/${filename}` }],
      };
    }
  • src/index.ts:167-180 (registration)
    Registration of the 'sc_record_start' tool in the tools array, including its name, description, and input schema definition for filename.
    {
      name: 'sc_record_start',
      description: 'Start recording audio output to a file',
      inputSchema: {
        type: 'object',
        properties: {
          filename: {
            type: 'string',
            description: 'Output filename (will be saved in recordings/ directory)',
          },
        },
        required: ['filename'],
      },
    },
  • Input schema definition for the 'sc_record_start' tool, specifying the required 'filename' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        filename: {
          type: 'string',
          description: 'Output filename (will be saved in recordings/ directory)',
        },
      },
      required: ['filename'],
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 ('Start recording') but omits critical details: whether this requires specific permissions, if it overwrites existing files, how long recording lasts, or what happens on errors. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 that directly states the tool's purpose with zero wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 (a mutation operation with no annotations or output schema), the description is incomplete. It lacks details on behavioral traits (e.g., file handling, recording duration), error conditions, or output expectations, leaving significant gaps for an AI agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'filename' documented in the schema as 'Output filename (will be saved in recordings/ directory)'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 ('Start recording') and resource ('audio output to a file'), distinguishing it from sibling tools like sc_record_stop (which stops recording) and sc_play_* tools (which play audio). It precisely defines the tool's function without ambiguity.

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 for initiating audio recording, but provides no explicit guidance on when to use this tool versus alternatives (e.g., sc_record_stop to stop, or sc_play_* tools for playback). It lacks context about prerequisites or exclusions, leaving usage inferred rather than stated.

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