Skip to main content
Glama

edit_notes

Edit notes by index within a VOCALOID6 part to change position, duration, pitch, lyric, phoneme, velocity, language, or vibrato.

Instructions

Change position, length, pitch, lyric, phoneme, velocity, language or vibrato of notes by index. / 番号で指定した音符の位置・長さ・音高・歌詞・発音記号・ベロシティ・言語・ビブラートを変更します

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

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
editsYes
trackYes

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 provided, so the description carries the full behavioral burden for a mutation tool. It does not disclose whether omitted fields are left untouched or reset, what happens if an index is out of range, whether edits are applied atomically, or whether the caller needs a specific track/part context.

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?

A single front-loaded sentence is efficient, but the long comma-separated field list and the duplicated Japanese translation add bulk without new meaning for an English-reading agent.

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 mutation tool with no annotations, no output schema, and undocumented top-level parameters, the definition leaves critical gaps: partial-update semantics, index scoping by track/part, and error behavior. What an agent needs to invoke it correctly is not fully covered.

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?

The prose mirrors the NoteEdit fields and confirms batch-style editing, but top-level parameters track, part, and path have no description anywhere in the schema, and the description adds nothing about how track/part scope the indices. With nested field descriptions present but 0% top-level coverage, this only partially compensates.

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 concrete verb ('Change') plus the resource ('notes') and enumerates the exact editable attributes (position, length, pitch, lyric, phoneme, velocity, language, vibrato) with the selector ('by index'). This clearly separates it from add_notes/delete_notes, though no sibling is named explicitly.

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?

The description says what can be changed but never says when to use this tool versus add_notes, delete_notes, or assign_lyrics, nor that indices must first be obtained (e.g. via list_notes). Usage is only inferable from 'by index'.

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