Skip to main content
Glama

list_notes

Retrieve the notes for a VOCALOID track part, including lyrics, phonemes, language, and vibrato, to inspect or edit a project's vocal melody.

Instructions

Notes of a part with lyric, phoneme (null = not computed yet), language, vibrato. / パートの音符一覧(歌詞・発音記号(null は未計算)・言語・ビブラート)

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": "list_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
countNo
startNo
trackYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add one genuinely useful behavioral fact — that a null phoneme means 'not computed yet' — but it never states that this is a read-only operation, what permissions or running-app state are required, or that count/start imply paging.

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 returned fields are front-loaded and the sentence has no filler. The bilingual duplication doubles the length without adding information, but it serves a locale purpose and does not obscure the meaning.

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?

An output schema exists, so return values need not be re-explained, yet the definition is silent on the five input parameters, on safety behavior, and on required app state. For a paged, two-required-parameter read tool with zero annotation coverage, this is under-specified.

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 five parameters, so the description must compensate and does not. It never explains track vs part, the meaning of path, or that count and start control pagination, leaving half the argument surface undocumented in both schema and prose.

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 the resource precisely: notes of a given part, and even enumerates the fields returned (lyric, phoneme, language, vibrato). It reads as a retrieval operation and is distinguishable from sibling mutators such as add_notes, edit_notes and delete_notes, though the verb ('list') 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 when-to-use or when-not-to-use guidance and no mention of alternatives such as get_project or get_curve. It also omits prerequisites implied by the sibling set (launch_vocaloid, open_project) and the fact that track and part identifiers must already be known.

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