Skip to main content
Glama

Convert song formats

convert
Read-onlyIdempotent

Use this when a song should move between MTL text, a Moose Tracker .mtk project, a share link and standard files: MIDI (.mid) and MOD, XM, S3M or IT tracker modules, in either direction (files in as base64; a written file comes back as a download link). It takes a song into another program (a DAW, a notation app, another tracker) or brings one in; voices maps channels to sample packs or presets on import, and feel adds swing or humanize. Cues and macros are compiled away in .mtk and share links. Schema a964948f.

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": {
      "from": "<from>",
      "to": "<to>",
      "input": "<input>"
    },
    "name": "convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
feelNoe.g. swing=60 hum=6
fromYes
inputYesThe song, .mtk JSON or share link; for mid, mod, xm, s3m and it, the file as base64 (up to about 700 KB)
namesNo
voicesNoSlot: pack, preset or line {"1":"upright-bass"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 826121bd"New value: +"Schema a964948f"
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d544474"New value: +"Schema 826121bd"
  3. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0781812e"New value: +"Schema 2d544474"
  4. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0d11f08d"New value: +"Schema 0781812e"
  5. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d7abb8b"New value: +"Schema 0d11f08d"
  6. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema ff675289"New value: +"Schema 2d7abb8b"
  7. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2a55f659"New value: +"Schema ff675289"
  8. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 71227a86"New value: +"Schema 2a55f659"
  9. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 64bfe66c"New value: +"Schema 71227a86"
  10. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema eb59845f"New value: +"Schema 64bfe66c"
  11. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 3b8fe45c"New value: +"Schema eb59845f"
  12. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
  13. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
  14. Changed4 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema d568427c"New value: +"Schema 415a8741"
    • addedInput schema / properties / feel
      Added value: +{
      +  "description": "e.g. swing=60 hum=6",
      +  "type": "string"
      +}
    • addedInput schema / properties / names
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / voices
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Slot: pack, preset or line {\"1\":\"upright-bass\"}",
      +  "type": "object"
      +}
  15. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
  16. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Schema 90ddc268"
  17. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety picture is supplied. The description adds genuinely useful behavior: base64 input, a download link for written files, and notably that cues and macros are compiled away in .mtk and share links, which warns of lossy output. However, it never reconciles that file-writing/download behavior with the read-only annotation, and adds no detail on failure modes or what a share link requires.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is correctly front-loaded with 'Use this when...', but the body is a dense run-on that packs format lists, base64 mechanics, voices, feel, and a lossy-conversion caveat into long clauses. The trailing 'Schema a964948f.' is pure noise with no informational value and should be removed.

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 6-parameter, 50%-coverage conversion tool with no output schema, the description covers most of what an agent needs: accepted format set, directionality, base64 input, download-link output, and the cue/macro compilation caveat. The main gap is the unexplained 'names' parameter and no sense of error behavior or what the returned link looks like.

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 50%, so the schema already documents 'input' (base64, ~700 KB limit) and 'feel' (swing/hum syntax). The description adds directional meaning for 'voices' (channel-to-pack/preset mapping applies on import) and clarifies the swing/humanize effect, which goes beyond the schema. But 'names' remains undocumented in both places, and the from/to enums need no explanation given their self-description.

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?

The description names a concrete transformation (moving a song between MTL text, .mtk projects, share links, MIDI, and MOD/XM/S3M/IT modules) and states it works in either direction. That is a specific verb-plus-resource statement an agent can act on. It stops short of explicitly distinguishing itself from siblings like 'render' or 'song', leaving some ambiguity about which tool handles a format change versus a rendering job.

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?

It gives clear situational triggers ('takes a song into another program - a DAW, a notation app, another tracker - or brings one in'), which maps well to the conversion use case. There are no explicit exclusions or named alternatives, so an agent still has to infer that 'render' or 'song' are not the right tools for a format change.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources