Skip to main content
Glama

convert_music

Converts MIDI, ABC notation, and MusicXML music files into JSON for structured parsing, editing, or data processing.

Instructions

Convert music notation and MIDI files: MIDI (.mid/.midi)→JSON, ABC notation (.abc)→JSON, MusicXML (.musicxml/.mxl)→JSON

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input music file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully discloses that every supported input maps to JSON output, but says nothing about whether an existing outputPath is overwritten, whether the input file must exist, or how unsupported/corrupt files fail.

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 the conversion mapping laid out as a compact arrow list; no filler, no repetition of the schema's path parameters.

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 4-parameter conversion tool with a fully described schema and no output schema, the description covers scope and output format adequately. The remaining gaps are file-overwrite semantics and any hint at the JSON structure produced.

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%, so both paths, the auto-detection default, and the format enums are already documented. The description reinforces the extension-to-format mapping (.mid/.midi, .abc, .musicxml/.mxl) but adds no semantics beyond the schema, which is the expected baseline.

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?

States a specific verb (convert) and resource (music notation/MIDI files) and enumerates the exact supported input formats with their file extensions. The format list implicitly separates it from siblings like convert_audio and convert_document, though no sibling is named explicitly.

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?

Usage is implied by the enumerated format list — an agent can infer this tool handles .mid/.abc/.musicxml inputs — but there is no explicit when-to-use statement, no mention of batch_convert for multiple files, and no prerequisites such as the input file needing to exist.

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