Skip to main content
Glama

assign_lyrics

Assign lyrics to existing notes from a specified start note by splitting text into one syllable per note or supplying a ready lyric list.

Instructions

Put lyrics on existing notes from note start on: text is split one syllable per note (see the rules), or pass lyrics as a ready list. / 既存の音符(start 番から)に歌詞を付けます。text は1音符1音節に分割、 または lyrics にリストで渡します。

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>"
    },
    "name": "assign_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
textNo
startNo
trackYes
lyricsNo
languageNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a mutation of existing notes but never says whether pre-existing lyrics are overwritten, what happens when the note range is shorter than the syllable count, what the response looks like, or that a Vocaloid session must be open. The unresolved '(see the rules)' reference adds no information.

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 core sentence is well front-loaded, but the description is fully duplicated in Japanese, roughly doubling length without adding information, and it wastes words on a dangling '(see the rules)' pointer that resolves to nothing.

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?

A 7-parameter mutation tool with no annotations, no output schema, and 0% schema coverage needs more than this: only three of seven parameters are addressed and no behavioral side effects are described, leaving an agent unable to call it safely from the definition alone.

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% across 7 parameters, and the description only explains `text`, `lyrics`, and `start`. `track`, `part`, `path`, and especially `language` (default 'auto') are left entirely undefined, including whether `path` is a project file selector or something else.

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?

States a specific verb and resource ('Put lyrics on existing notes') with a scope anchor ('from note `start` on'), and names the two input modes (raw `text` vs a ready `lyrics` list). It is distinguishable from note-creation siblings, though it never names `split_lyrics`, which sounds adjacent.

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 either/or between `text` and `lyrics` is stated, so an agent knows the two input modes are alternatives. However, there is no guidance on when to prefer this over `split_lyrics`, no prerequisites about existing notes needing to be present, and the pointer '(see the rules)' references rules that are not included.

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