Skip to main content
Glama

edit_track

Rename, mute, solo, set volume or pan, and change the singer of VOCALOID tracks or parts by specifying a track and desired properties.

Instructions

Rename, mute, solo, set volume (dB x10) / pan (-64..64), or change the singer of every part. / トラック名・ミュート・ソロ・音量(dB×10)・パン(-64〜64)・全パートの歌手を変更します

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

Input Schema

NameRequiredDescriptionDefault
panNo
muteNo
nameNo
pathNo
soloNo
trackYes
voiceNo
volumeNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/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. It discloses that singer changes apply to every part and gives units/ranges for volume and pan, but does not explain reversibility, prerequisites, whether edits are immediate, or what happens to omitted fields.

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 description is front-loaded and dense, listing the editable operations in one sentence. The English/Japanese duplication doubles the length, and the slash between volume and pan is slightly ambiguous, but the structure remains clear.

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 9-parameter mutation tool with no annotations and no output schema, the description is incomplete. It lacks semantics for track, path, and language, and does not cover side effects or return behavior, so an agent cannot fully infer correct invocation from this 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 9 parameters, and the description only maps name, mute, solo, volume, pan, and loosely voice. It omits the required track parameter and leaves path and language undocumented, though the volume/pan units and ranges add meaningful value.

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 resource (track) and enumerates editable properties, so it is clear this edits an existing track. It does not explicitly distinguish itself from edit_part beyond saying the singer change affects every part, so it is strong but not fully differentiated.

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 explicit guidance on when to use edit_track versus siblings such as edit_part, add_track, or remove_track. The list of operations implies editing, but that is purpose rather than usage guidance.

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