Skip to main content
Glama

add_notes

Add multiple notes with positions, durations, and lyrics to a VOCALOID6 track part, automatically extending the part length to fit the inserted notes.

Instructions

Add notes (positions relative to the part; the part grows to fit). / 音符を追加します(位置はパート相対、パートは自動で伸びます)

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

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
notesYes
trackYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/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 disclosure burden. It does add one genuinely useful behavioral trait the schema does not state: the part automatically grows to fit the added notes. It says nothing about required connection state, how overlapping or duplicate notes are handled, or whether the call is reversible, which leaves significant gaps for a write operation.

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?

A single front-loaded sentence with the key behavioral qualifier in parentheses; the bilingual restatement is duplicative but conventional for this server. Nothing is padded or buried.

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?

For a 5-parameter mutation tool with zero annotations, no output schema, and 0% top-level schema descriptions, the definition is thin. It omits preconditions (does a project/Vocaloid session need to be open?), what is returned (created note handles ids?), and conflict behavior with existing notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema coverage is 0%, but the nested NoteIn properties are self-documented. The description adds real meaning for the trickiest field by specifying that position is measured relative to the part start, and explains the resulting part-length behavior. The track, part, path, and language parameters remain unexplained beyond their names.

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 states a specific verb (add) and resource (notes) and clarifies the scope of the position field as part-relative. It does not name or distinguish itself from close siblings such as add_melody or edit_notes, so it stops short of a 5.

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 when-to-use guidance, no mention of prerequisites (a loaded project, an existing track/part id), and no routing to alternatives like edit_notes or add_melody. The agent must infer the use case purely from the verb.

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