Skip to main content
Glama

add_part

Adds an empty part to a VOCALOID6 track at an absolute position, using the track singer unless a voice is specified.

Instructions

Add an empty part (absolute position). Uses the track's singer unless voice is given. / 空のパートを追加します(絶対位置)。voice を省くとトラックの歌手を使います

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

Input Schema

NameRequiredDescriptionDefault
nameNo
pathNo
trackYes
voiceNo
durationNo
languageNo
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. It does disclose one useful behavior (the part inherits the track's singer unless voice is given) and that the part is created empty, but it says nothing about whether this mutates the project irreversibly, what the default duration of 1920 means, or what is returned on success.

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 definition is short and front-loads the verb and resource, with the key default-behavior note second. The bilingual duplication restates the identical content in Japanese, which adds length without adding information for most consumers, though it does not obscure anything.

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 seven-parameter mutation with no annotations and no output schema, the description is thin: it leaves five parameters undocumented and gives no indication of the result or error behavior. An agent would have to guess at duration units and whether path/name must be supplied.

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?

Schema description coverage is 0% across seven parameters, so the description must compensate. It clarifies two of them meaningfully — position is absolute (not relative) and voice is optional with a track-singer fallback — but name, path, track, duration, and language get no explanation at all, leaving units and formats ambiguous.

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 names a specific verb and resource ('Add an empty part') and adds a scope qualifier ('absolute position'), which separates it from content-adding siblings like add_melody and add_notes. It stops short of naming any sibling explicitly, so the differentiation is inferred 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: nothing says whether to call add_part before add_notes, how it relates to add_melody, or what preconditions (existing track, project open) must hold. The only conditional statement is about voice defaulting, which is parameter behavior rather than usage routing.

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