Skip to main content
Glama
Sign In
cochlea

cochlea

by richer-richard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

export_midi

Convert a cochlea RON score into a Standard MIDI File, preserving timing and tempo, for export to DAWs or notation tools.

Instructions

Convert a cochlea RON score into a Standard MIDI File (format 1) — the inverse of import_midi. Timing exports exactly (score ticks become SMF ticks, the tempo map and time signature carry over); instruments become rough General MIDI program labels, since a synth preset isn't a GM instrument. Use this to hand a composed score to a DAW or notation tool, or to round-trip through external MIDI editing.

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": "export_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
out_pathYesWhere to write the Standard MIDI File (.mid).
score_pathYesPath to a RON score file (data form version 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses that timing is exact, instruments become rough GM program labels (not exact), and output is format 1, providing valuable behavioral context.

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 sentences, front-loaded with core purpose, no wasted words, efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, complete schema, and no output schema, the description sufficiently covers purpose, behavior, and usage, leaving no critical gaps.

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 coverage is 100% with descriptions for both parameters. The description adds minimal extra meaning beyond schema, such as clarifying that the output is a Standard MIDI File; baseline 3 is appropriate.

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 states the tool converts a cochlea RON score to a Standard MIDI File (format 1) and explicitly names the inverse tool 'import_midi', clearly distinguishing its purpose from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit use cases: hand a composed score to a DAW or notation tool, or round-trip through external MIDI editing, and implies when not to use (if exact instrument presets are needed) by noting instruments become rough GM labels.

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