Moose Tracker

Convert song formats

convert

Read-onlyIdempotent

Use this when you need to move a song between MTL text, a Moose Tracker .mtk file, a share link, and standard files: MIDI (.mid), and MOD, XM, S3M or IT tracker modules (read and write; files are base64). Cues and macros are compiled away in .mtk and share links. Schema 3b8fe45c.

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

Name	Required	Description
`to`	Yes
`feel`	No	e.g. swing=60 hum=6
`from`	Yes
`input`	Yes	The song, .mtk JSON or share link; for mid, mod, xm, s3m and it, the file as base64 (up to about 700 KB)
`names`	No
`voices`	No	Slot: pack, preset or line {"1":"upright-bass"}

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026
- changedInput schema / description
```
Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
```
Changed1 schema field changedNov 9, 2026
- changedInput schema / description
```
Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
```

Changed4 schema fields changedNov 9, 2026

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"
+}

Changed1 schema field changedNov 4, 2026
- changedInput schema / description
```
Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
```
Changed1 schema field changedNov 3, 2026
- addedInput schema / description
```
Added value: +"Schema 90ddc268"
```
First observedOct 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes beyond the readOnly/idempotent annotations by disclosing a real behavioral consequence: cues and macros are compiled away in .mtk and share links, i.e. the conversion is lossy for those formats. It also notes files are base64 and readable/writable for tracker modules. It could say more about what the call returns, but the lossiness disclosure is genuinely useful information the annotations cannot convey.

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

Conciseness4/5

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

The trigger condition is front-loaded and the format list plus lossiness caveat are densely packed into two sentences. The trailing 'Schema 3b8fe45c.' is pure noise since the same string already appears in the schema description.

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

Completeness3/5

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

For a six-parameter, nested-object conversion tool with no output schema, the description never indicates the shape of the result (base64? share URL string? JSON?) or whether output format follows 'to'. The lossiness note helps, but the return-side gap and undocumented 'names'/'feel' parameters leave the definition incomplete.

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?

With only 50% schema description coverage, the description must compensate, and it only partly does: it clarifies that non-MTL/MIDI formats are base64 payloads and that from/to cover the same format set. It says nothing about the undocumented 'names' parameter, the 'voices' slot/preset/line semantics, or what 'feel' expressions like swing=60 mean beyond the schema's example.

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?

States a specific verb+resource ('move a song between') and enumerates every supported format: MTL text, .mtk, share link, MIDI, and MOD/XM/S3M/IT modules. An agent can immediately distinguish this transformation tool from siblings like render, song, or assets.

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?

'Use this when you need to move a song between...' gives a clear trigger condition for the tool. It does not name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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

All Moose Tracker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?