Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

plugin_add_drum_kit

Add a sampler-based drum kit to a track by defining pads with MIDI notes and sample paths, automatically mapping each pad to a single note and applying optional gain, pan, and decay settings.

Instructions

Add a Sampler-backed drum kit to a track. pads is a list of {midi_note, sample_path, name?, gain_db?, pan?, decay?}. Each pad becomes one SOUND mapped to a single MIDI note. Replaces the manual Sampler+sounds boilerplate in compose_lofi_track.

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_id": "<track_id>",
      "pads": "<pads>"
    },
    "name": "plugin_add_drum_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoDrum Kit
padsYes
track_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral disclosure burden. It does disclose the Sampler-backed nature, the one-pad/one-MIDI-note mapping, and that it automates boilerplate. It does not state side effects, reversibility, or what happens to existing track contents, leaving a meaningful 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?

Three compact sentences front-load the action, then provide the pad structure, behavior, and context. No filler or restatement of the schema.

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 mutation tool with no annotations and no output schema, the description omits return values, error behavior, and side effects on the target track. It is sufficient for a straightforward call but not fully complete for confident invocation.

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%, and the description partially compensates by defining pads as a list of {midi_note, sample_path, name?, gain_db?, pan?, decay?} and explaining pad-to-note mapping. It does not explain track_id or name, nor the units/semantics of gain_db, pan, and decay, so the compensation is incomplete.

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 and resource ('Add a Sampler-backed drum kit to a track') and clarifies the pad-to-SOUND/MIDI-note mapping. It also distinguishes itself from generic plugin_add by describing drum-kit-specific behavior and by noting it replaces manual Sampler boilerplate.

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?

Description tells the agent this is the intended way to add a drum kit and that it replaces manual Sampler+sounds boilerplate in compose_lofi_track. It does not explicitly list exclusions or compare against sibling tools like plugin_add, but the context is clear enough.

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