Skip to main content
Glama

remove_track

Deletes a track from a VOCALOID6 project or editor session. Use it to remove unwanted tracks by specifying the track number and optional project path.

Instructions

Delete a track. / トラックを削除します

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

Input Schema

NameRequiredDescriptionDefault
pathNo
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Delete" implies an irreversible mutation, yet the description says nothing about whether the operation is undoable, whether child data (notes, parts, curves) is cascaded away, whether a confirmation step exists, or what happens on an invalid track index.

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?

Extremely short and front-loaded: the verb-resource statement leads and there is no filler. The bilingual duplication adds no information for the primary reader, which is the only minor inefficiency.

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 destructive mutation tool with zero annotations, no output schema, and 0% parameter documentation, this description is far too thin. An agent cannot determine reversibility, side effects, or the meaning of the optional path parameter before invoking it.

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%, so the description must compensate, and it only vaguely gestures at "track" without explaining indexing, valid range, or consequences. The second parameter "path" is never alluded to at all, leaving half the inputs undocumented in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete a track" states a specific verb and resource, but it largely restates the tool name remove_track rather than adding distinguishing detail. It does not clarify scope (e.g. whether the track's notes/parts go with it) or distinguish it from siblings like remove_part or delete_notes.

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, no mention of prerequisites, and no reference to alternatives such as remove_part (removing a part) or delete_notes (removing contents without removing the track). The agent must infer selection criteria entirely from the name.

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