Skip to main content
Glama
francescojr

nobu

by francescojr

add_layer

Add an independent layer (melody, harmony, bass, or drums) to a chiptune project by specifying notes, timing, and optional swing offset for humanization.

Instructions

Add ONE independent layer/channel to the project. Call this tool multiple times to stack as many layers as you want (melody, harmony, bass, drums) — each layer has its own length and rhythm, without needing to match the others in note count.

layer_type accepts: 'melody', 'harmony', 'bass', 'drums'.

Format of 'notes': each item is [pitch_or_piece, start_time_in_beats, duration_in_beats, optional_velocity_0_to_127]. If layer_type='drums', pitch may be a string ('kick', 'snare', 'closed_hihat', 'open_hihat', 'crash', 'ride', 'clap', 'rimshot', 'low_tom', 'mid_tom', 'high_tom') or a GM percussion MIDI number. Portuguese drum names are also accepted.

swing_offset: add a fixed offset (in beats, e.g. 0.02 to 0.08) to every ODD-index note, simulating light swing/humanization. Use 0.0 for straight quantized rhythm (classic chiptune aesthetic). For deliberate off-beats (e.g. hi-hat on 0.5, 1.5, 2.5), place start_time directly in the notes list — no swing_offset needed.

chiptune_program (ignored if layer_type='drums'): 'pulse_lead' (melody, NES pulse timbre, GM 80), 'pulse_harmony' (countermelody, GM 81), 'triangle_bass' (bass, NES triangle approx, GM 38).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
layer_nameYes
layer_typeYes
midi_channelNo
project_nameYes
swing_offsetNo
chiptune_programNopulse_lead

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It details note format, layer_type values, swing_offset behavior (applied to odd-index notes), and that chiptune_program is ignored for drums. Missing details on side effects or permissions, but adequate for core behavior.

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 a single paragraph with clear structure: purpose, stacking instruction, then parameter details. It is informative without being overly verbose, though could be slightly tighter.

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?

Given 7 parameters (4 required), nested arrays, no annotations, and an output schema, the description covers the key aspects. It explains independent layers, note formatting, swing, and chiptune programs. It omits error conditions and limits, but is sufficient for typical use.

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 description coverage is 0%, so the description compensates well. It explains the notes array format, accepted layer_type values, swing_offset usage, and chiptune_program options. It does not describe midi_channel, but other parameters are well covered.

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 clearly states 'Add ONE independent layer/channel to the project', specifying a concrete action and resource. It gives examples of layer types (melody, harmony, bass, drums) and explains stacking via multiple calls, distinguishing it from siblings like list_layers.

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?

The description explains that the tool can be called multiple times to stack layers, each with its own length and rhythm. It does not explicitly state when not to use it or compare to alternatives, but the context is clear.

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/francescojr/nobu'

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