Skip to main content
Glama

get_drum_map

Read a track's Drum Rack pads and their assigned roles—kick, clap, hats, percussion—including MIDI notes, names, and devices, to map drums before writing patterns.

Instructions

The Drum Rack on a track: every filled pad (MIDI note, name, devices) and the role each one plays (kick, clap, closed_hat, open_hat, rim, ride, perc...), read from the pad names, as used by write_drum_pattern.

Parameters:

  • track_index: Track holding the Drum Rack

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>"
    },
    "name": "get_drum_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does add genuinely useful disclosure that roles are inferred 'from the pad names' — telling the agent the classification is heuristic and may be wrong — but it never states the operation is read-only, what happens if the track holds no Drum Rack, or whether unfilled pads appear.

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?

Front-loaded with the resource and returned fields, then a short parameter note; no filler sentences. The parenthetical list of role values is dense but earns its place by showing the output vocabulary.

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

Completeness5/5

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

This is a simple one-parameter read tool with an output schema, so return values need no prose explanation. The description covers what is returned, how roles are derived, and the one parameter's constraint — enough for correct invocation without redundancy.

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 coverage is 0%, so the description must carry the lone parameter, and it does: 'track_index: Track holding the Drum Rack' supplies a constraint the bare 'Track Index' title does not. The remaining gap is that nothing is said about valid index ranges or what an invalid index returns.

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 resource (the Drum Rack on a track) and enumerates the returned content: pad MIDI note, name, devices, plus an inferred role. That is far more than a restatement of the name. It does not explicitly distinguish itself from sibling readers like get_device_info or get_track_info, so it falls short of a 5.

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 phrase 'as used by write_drum_pattern' hints at the workflow context (inspect the map before writing patterns) but never states the condition for calling it or when another tool is preferable. Usage is implied rather than prescribed, which is the definition of a 3.

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