Skip to main content
Glama

add_track

Creates a track for a specified voicebank with one empty part, and sets the AI voice language for AI voicebanks.

Instructions

Add a track for a voicebank (VOCALOID:AI track for AI banks, VOCALOID track for classic ones) with one empty part. language picks the AI voice's language (ja/en/ko/es/zh). / 音源のトラックを追加します(AI 音源は VOCALOID:AI、旧世代は VOCALOID トラック)。空のパートを1つ作ります。language は AI 音源の言語です。

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": {
      "voice": "<voice>"
    },
    "name": "add_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pathNo
voiceYes
languageNo
part_durationNo
part_positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/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 burden; it does disclose that a track plus one empty part is created and that language only affects AI banks. It omits prerequisites, whether the new track becomes active, and whether the operation is reversible. That is useful but incomplete behavioral context for a mutation tool.

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?

The core information is front-loaded in the first sentence, but the entire content is then repeated in Japanese, roughly doubling length without adding information. The redundancy dilutes rather than harms the definition.

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 six-parameter mutation tool with no annotations and no output schema, the description covers only a fraction of what an agent needs: most parameters, prerequisites, and return behavior are undocumented. The language detail is a genuine plus, but overall it is under-specified relative to complexity.

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 6 parameters, so the description must compensate and it only partly does: it explains voice implicitly and gives concrete values for language (ja/en/ko/es/zh). name, path, part_duration, and part_position get no explanation anywhere, leaving four of six parameters opaque.

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 specific verb and resource ('Add a track for a voicebank') and clarifies the track type mapping (VOCALOID:AI for AI banks, VOCALOID for classic). It also discloses the side effect of creating one empty part. It does not distinguish itself from close siblings such as add_part or edit_track, 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 and no mention of alternatives; an agent cannot tell from this text whether to call add_track versus add_part or edit_track. Prerequisites (project must be open, voicebank must exist) are also unstated.

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