Skip to main content
Glama

remove_part

Deletes a specified part from a track in a VOCALOID6 project, using an optional project path, to remove unwanted song sections.

Instructions

Delete a part. / パートを削除します

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

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.2/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 burden, yet it only says 'Delete'. It does not state whether deletion is reversible, what happens to notes or clips inside the part, whether a track must be empty, or what permissions/state are required.

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?

It is short and front-loaded, but the bilingual duplication doubles the text without adding meaning, and the brevity stems from under-specification rather than efficiency.

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, three-parameter operation with no annotations, no output schema, and zero parameter documentation, the description leaves too much unspecified for an agent to call it safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters (track, part, path), and the description explains none of them. In particular the optional 'path' parameter and the relationship between 'track' and 'part' identifiers are left completely undocumented.

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?

The description has a specific verb ('Delete') and resource ('part'), which nominally separates it from siblings like remove_track and remove_tempo. However, it gives no indication of what a 'part' is or how it relates to tracks, and the Japanese half is a verbatim translation that adds no distinguishing information.

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, no prerequisites, and no mention of alternatives such as edit_part or remove_track for related removal tasks. The agent must infer entirely from the tool name.

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