Skip to main content
Glama
Sign In
cochlea

cochlea

by richer-richard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

render_score

Turn a declarative RON score into a deterministic WAV mix for listening or inspection. Enable verify to run embedded assertions and receive a pass/fail report.

Instructions

Render a cochlea RON score (the declarative tick/track/note/automation IR) to a deterministic WAV mix. Use this to turn a composed score into audible PCM before probing or inspecting it. Set verify=true to also run the score's embedded verify: assertions and get the pass/fail report back in the same call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "score_path": "<score_path>",
      "out_path": "<out_path>"
    },
    "name": "render_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitsNoPCM encoding for the WAV: 'float' (32-bit, lossless, the render's ground truth — default), '24', or '16' (integer, for a small ordinary file).float
verifyNoRun the score's embedded verify: assertions after rendering and include the report; the tool call reports isError:true if verification fails. Default false.
out_pathYesWhere to write the rendered mix (stereo WAV).
stems_dirNoOptional directory to also write one WAV per track (created if missing).
score_pathYesPath to a RON score file (data form version 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / bits
      Added value: +{
+  "default": "float",
+  "description": "PCM encoding for the WAV: 'float' (32-bit, lossless, the render's ground truth — default), '24', or '16' (integer, for a small ordinary file).",
+  "enum": [
+    "float",
+    "24",
+    "16"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / out_path / description
      Previous value: -"Where to write the rendered mix (32-bit float stereo WAV)."New value: +"Where to write the rendered mix (stereo WAV)."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses key behaviors: the render is deterministic, and the verify parameter triggers assertions with isError result. However, it does not cover authorization or rate limits.

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?

Two concise sentences with no filler. First sentence states primary purpose, second explains additional feature (verify). Ideal front-loading.

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 tool that writes output to a file and has no output schema, the description covers the key behavior (rendering to WAV and optional verify report). It does not describe the return value format, but the context is sufficient for basic usage.

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%, so baseline is 3. The description adds value for the verify parameter (explaining the error behavior) but does not provide additional meaning beyond schema for other parameters.

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?

Clearly states the verb 'render', the resource 'cochlea RON score', and the output 'deterministic WAV mix'. The description distinguishes the tool from siblings like probe_audio or spectrum by specifying its unique purpose of converting a score to audio.

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?

Provides explicit context: 'Use this to turn a composed score into audible PCM before probing or inspecting it.' This guides the agent on when to use the tool, though it does not mention when not to use it or alternative tools.

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