Skip to main content
Glama

create_midi_track

Adds a MIDI track for instruments or drum racks at a chosen position, or after the last track when index is -1.

Instructions

Add a MIDI track (for instruments and drum racks).

Parameters:

  • index: Where to insert it (-1 = after the last track)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_midi_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says nothing about whether the new track is selected, armed, or named, what happens with an out-of-range index (error vs. clamp vs. append), or whether the operation is reversible. For a state-mutating tool with zero annotation coverage, this is a significant gap.

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 lines, front-loaded with the action and immediately followed by the one parameter that needs explanation. No filler and nothing redundant.

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?

An output schema exists so return values need not be described, and the tool is a simple one-parameter mutation. The definition covers purpose and the index convention, but leaves side effects on the session (selection, naming, placement relative to selected track) undocumented, which matters for a mutation tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, so the description must compensate. It does explain that index is the insertion position and that -1 appends after the last track, which is real meaning beyond the bare schema default. It omits bounds/error behavior for out-of-range or negative values other than -1.

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 and resource ('Add a MIDI track') and adds a qualifier that narrows its domain to instruments and drum racks, which implicitly separates it from create_audio_track. It stops short of explicitly naming or contrasting the sibling, so it is clear but not fully differentiated.

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?

The parenthetical '(for instruments and drum racks)' implies when to prefer this over an audio-track tool, but there is no explicit when-to-use statement, no prerequisites, and no mention of alternatives such as create_audio_track or import_midi_file. Usage must be inferred.

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