Skip to main content
Glama

load_drum_kit

Load a Drum Rack onto a MIDI track, then load the first available kit from a specified browser folder.

Instructions

Load a Drum Rack, then the first loadable kit found in a browser folder.

Parameters:

  • track_index: A MIDI track

  • rack_uri: URI of the Drum Rack to load first

  • kit_path: Browser folder holding the kits, e.g. "drums/Drum Hits"

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": {
      "track_index": "<track_index>",
      "rack_uri": "<rack_uri>",
      "kit_path": "<kit_path>"
    },
    "name": "load_drum_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kit_pathYes
rack_uriYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.8/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 discloses the useful two-step sequencing (rack first, then the first loadable kit), but says nothing about whether existing devices on the track are replaced, what occurs if no loadable kit exists in the folder, or any permission/side-effect profile for what is clearly a mutation.

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 summary sentence is front-loaded and the parameter block is scannable with zero filler. Restating the parameter names earns its place given the schema has no field descriptions, though the glosses themselves could be denser with information.

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?

The return value is covered by the existing output schema, so the description needn't explain it. However, for a three-required-parameter mutation with no annotations, the definition omits failure behavior, replacement semantics, and precise parameter formats, which an agent would need to call it correctly the first time.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and only partly does. The kit_path example ('drums/Drum Hits') genuinely clarifies the expected format, but 'track_index: A MIDI track' is vague about whether it is a positional index or a track identifier, and rack_uri's expected URI form is unstated.

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 specific verb and resource ('Load a Drum Rack') and adds a non-obvious second step: the first loadable kit found in a browser folder. That two-stage behavior distinguishes it meaningfully from a generic loader, though it never names the closest sibling (load_instrument_or_effect) to contrast with.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. The description never says what precondition makes this the right choice over load_instrument_or_effect, nor what happens if a MIDI track already contains a device, leaving the agent to infer the selection context.

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