Skip to main content
Glama

mcp_opendaw_create_counterpoint

Generate a counter-melody in contrary motion to existing notes by mirroring pitch around a midpoint offset by a chosen interval, creating harmonic interest.

Instructions

Generate a counter-melody in contrary motion to existing notes.

Reads notes from a melody and creates a counterpoint that moves in the opposite direction: when the melody goes up, the counterpoint goes down, and vice versa. Each note is offset by a fixed interval from the melody's midpoint pitch, then mirrored.

unit_index: Source AU index. track_index: Source note track index. region_index: Source region index. interval: Base interval in semitones between melody and counterpoint (default 7 = fifth). The counterpoint is placed interval semitones below the melody's average pitch, then each note is mirrored around that center. new_unit_index: Target AU index (-1 = create new synth track). new_track_index: Target note track index on the target AU. velocity: Velocity for counterpoint notes (default 0.6, quieter than melody).

Returns source notes read and counterpoint notes created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intervalNo
velocityNo
unit_indexYes
track_indexNo
region_indexNo
new_unit_indexNo
new_track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description explains the algorithm, that it reads notes and creates new ones, and returns counts. It does not mention side effects (e.g., non-destructive read) but is otherwise thorough.

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 well-structured: concept overview, then parameter list, then return note. It is concise (about 150 words) and front-loaded with purpose.

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?

Covers algorithm, parameters, and return values. Missing preconditions (e.g., source track must have notes) and edge cases. Output schema exists but description mentions return structure anyway.

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 coverage is 0%, so the description must explain all 7 parameters. It does so with clear explanations (e.g., interval default and usage, velocity quieter, new_unit_index -1 means new track).

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?

The description starts with a clear verb and resource: 'Generate a counter-melody in contrary motion to existing notes.' It explains the concept and distinguishes from siblings like create_canon or create_fugue.

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 description implies use when wanting contrary motion counterpoint but does not explicitly state when to use this vs alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AMEOBIUS-team/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server