Skip to main content
Glama

write_bassline

Creates a kick-aligned bassline from a reference bass, key, or MIDI root; choose a style, preview the piano roll, then write it to a bass track slot.

Instructions

A bassline that sits under the kick: root from the reference's bass (or the key, or root as a MIDI pitch), kick grid from a drum clip or the last capture. style: sub_hold, rolling_offbeat, follow_kick, two_note. dry_run shows the piano roll; dry_run=false writes it to slot slot of the bass track (created if missing) or track, replacing what is there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
rootNo
slotNo
styleNosub_hold
trackNo
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a good job: it discloses root selection priority, style options, dry_run behavior, track creation, and that existing content is replaced. The only notable omission is what the bars parameter controls, but the main write and replace semantics are transparent.

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 description is compact and front-loaded with the core purpose, and nearly every clause adds information. It is a single dense run-on rather than clearly separated sentences, but there is little waste and the key behavioral details are packed efficiently.

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 description covers side effects, destination selection, root resolution, and style options, which is strong for a tool without annotations. However, the bars parameter is unexplained, the term 'last capture' is not defined, and there is no guidance on style selection or interaction with sibling bass-design tools. The output schema presumably covers return values, so that part is acceptable.

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 explain the parameters, and it explains most of them: root, style, dry_run, slot, and track. The bars parameter is entirely undocumented, which is a real gap, but the description adds substantial meaning beyond the bare schema for the other five parameters.

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 clearly states what the tool produces: a bassline synced to the kick, with configurable root, style, and write target. It lacks an explicit verb at the start and does not differentiate itself from sibling tools like design_bass or find_bass_patches, but the resource and behavior are clear.

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?

The description implies when this tool is used—when a bassline under the kick is needed—but gives no explicit guidance on when to choose it over alternatives. It also does not mention when to use dry_run versus a direct write, leaving that decision to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.