Skip to main content
Glama
BradA1878
by BradA1878

sc_status

Check the current status of the SuperCollider audio synthesis server, including whether it's running and its CPU usage.

Instructions

Get the current status of the SuperCollider server (running, CPU usage, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'sc_status' tool within the CallToolRequestSchema switch statement. It calls scServer.getServerStatus() and returns the status as a JSON string.
    case 'sc_status': {
      const status = await scServer.getServerStatus();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(status, null, 2),
          },
        ],
      };
    }
  • Input schema and tool metadata definition for 'sc_status', featuring an empty properties object indicating no input parameters.
    {
      name: 'sc_status',
      description: 'Get the current status of the SuperCollider server (running, CPU usage, etc.)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:200-202 (registration)
    Registration of the ListToolsRequestSchema handler, which exposes the tools array containing 'sc_status'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
  • SuperColliderServer.getServerStatus() method, which implements the core status checking logic by querying the SC server if booted.
    async getServerStatus(): Promise<{
      running: boolean;
      avgCPU?: number;
      peakCPU?: number;
      numUGens?: number;
      numSynths?: number;
      numGroups?: number;
      numSynthDefs?: number;
    }> {
      if (!this.isBooted) {
        return { running: false };
      }
    
      try {
        await this.executeCode('Server.default.queryAllNodes;');
        return {
          running: true,
          // Note: Getting real-time stats requires OSC monitoring
          // This is a simplified version
        };
      } catch (error) {
        return { running: false };
      }
    }
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 tool's purpose (read-only status retrieval) but lacks details on behavioral traits such as response format, latency, error conditions, or whether it requires the server to be running. The description is accurate but minimal.

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 front-loads the core purpose ('Get the current status') and provides clarifying examples. There is no wasted verbiage or redundancy.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally complete. It covers the basic purpose but lacks details on output format or behavioral context that could aid an agent in using it effectively, especially without annotations.

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 no parameter documentation is needed. The description does not add parameter semantics, but this is appropriate given the lack of parameters, warranting a baseline score above 3.

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 verb ('Get') and resource ('current status of the SuperCollider server'), with specific examples of what status includes ('running, CPU usage, etc.'). It distinguishes from siblings like sc_boot (start server), sc_quit (stop server), and sc_health_check (likely more detailed diagnostics) by focusing on real-time operational status.

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 checking server operational state, but does not explicitly state when to use this tool versus alternatives like sc_health_check or other siblings. No guidance on prerequisites, exclusions, or specific contexts is provided.

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