Skip to main content
Glama

add_melody

Adds a melody and matching lyrics to a VOCALOID part in one call, aligning one syllable per sounding note and letting start default to the part's end.

Instructions

Add a melody and its lyrics in one call. melody: 'A4:1 A4:1 B4:2 r:1 C5:1/2' (length in quarter-note beats, r = rest). lyrics are split one syllable per sounding note and must match the note count. start defaults to the end of the part's last note. / メロディと歌詞を一度に追加します。melody 例 'A4:1 A4:1 B4:2 r:1 C5:1/2' (長さは四分音符単位、r = 休符)。歌詞は1音符1音節に分割し、音符数と一致させてください。

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": "<track>",
      "part": "<part>",
      "melody": "<melody>"
    },
    "name": "add_melody"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
startNo
trackYes
lyricsNo
melodyYes
languageNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose real behavior: lyric syllables split one per sounding note, an error condition if counts mismatch, and that start defaults to the end of the part's last note (implying append semantics). It says nothing about permission/auth needs, whether an existing melody is overwritten, what happens on malformed note strings, or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English portion is well front-loaded with the core action followed by the notation example and the two key constraints. However, the entire block is then duplicated in Japanese, roughly doubling length without adding information for a single-language reader, which is a substantial token cost for a short tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Seven parameters, zero schema descriptions, no annotations, and no output schema make this a demanding definition, and the description covers only part of it. Four parameters (track, part, path, language) go completely undocumented, and mutation behavior for a write tool is only partially described.

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 only three of seven parameters are addressed: melody syntax (pitch:duration and r for rest), the lyrics one-syllable-per-note rule, and the start default. Track, part, path, and language are entirely unexplained in both the schema and the description, leaving the agent to guess their meaning and format.

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 uses a specific verb and resource ('Add a melody and its lyrics in one call') and conveys the distinctive value: melody plus lyrics in a single operation. It does not name a sibling such as add_notes or assign_lyrics as the alternative for note-by-note or lyrics-only workflows, so the differentiation is implied rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to siblings like add_notes or assign_lyrics, even though those overlap conceptually. The only implicit usage context is the note-string syntax example and the constraint that lyrics syllable count must equal note count.

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