Skip to main content
Glama

set_drum_choke

Assign Drum Rack pads to a choke group so they cut each other off, like closed and open hi-hats. Use group 0 to remove the choke.

Instructions

Put Drum Rack pads in a choke group so they cut each other — the classic: closed and open hi-hat together (e.g. notes [42, 46], group 1). Group 0 removes the choke.

Parameters:

  • track_index: Track with the Drum Rack

  • notes: Pad MIDI notes (see get_drum_map)

  • group: Choke group 1-16, or 0 for none

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

Input Schema

NameRequiredDescriptionDefault
groupNo
notesYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description still explains the core behavior: pads in the same group cut each other, and group 0 removes the choke. However, it does not disclose whether existing choke assignments are overwritten, what errors may occur, or any permission/precondition details beyond the track containing a Drum Rack.

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?

The description is short, front-loaded with the purpose, and organized into a compact parameter list. Every sentence adds useful information, including the example and the special group 0 behavior.

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 simple three-parameter mutation tool with an output schema, the description covers purpose, effect, and all parameter meanings well. It is slightly incomplete on edge cases such as overwriting existing choke groups or precondition failures, but it is sufficient to invoke the tool correctly.

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

Parameters5/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 carry parameter meaning, and it does: track_index identifies the Drum Rack track, notes are pad MIDI notes with a cross-reference to get_drum_map, and group is defined as 1-16 with 0 meaning none. This fully compensates for the bare schema.

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 gives a specific verb and resource: putting Drum Rack pads into a choke group so they cut each other. It clearly explains the effect, including the classic hi-hat example, though it does not explicitly contrast itself with sibling tools.

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 provides clear usage context by naming the classic closed/open hi-hat scenario and explaining that group 0 removes the choke. It does not give explicit when-not guidance or name alternatives, but the intended use is easy to infer.

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