Skip to main content
Glama
Sign In
SuperCollider OSC MCP

SuperCollider OSC MCP

by Tok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_example_osc

Plays a short test chime to verify that SuperCollider audio output is working before running a session.

Instructions

Play a short test chime to check that sound comes out.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "play_example_osc"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already disclose the safety profile: non-read-only, non-idempotent, non-destructive, closed-world. The description adds that the output is audible and brief ("short test chime", "sound comes out"), which is useful context beyond the annotations, but says nothing about whether playback blocks or how long the chime lasts.

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?

A single front-loaded sentence with no filler. The purpose and the reason to use it are both packed into ten words.

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?

For a no-parameter diagnostic tool with an output schema present, the description covers what it does and why. Only minor detail such as blocking behavior or chime duration is absent, and the output schema can carry the result shape.

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 takes zero parameters, so there is no schema semantics for the description to compensate for. Baseline 4 applies; nothing is missing on this dimension.

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?

"Play a short test chime" names a concrete action and resource, and the word "test" carves out a diagnostic role distinct from siblings like play_synth or play_melody. It stops short of explicitly contrasting itself with those siblings, but an agent can still place it correctly.

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 clause "to check that sound comes out" implies the use case (audio-output verification) rather than a musical playback. There is no explicit when-not guidance or named alternative, so the agent must infer that this is the smoke-test option among several sound-producing siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools