Skip to main content
Glama

edit_part

Move, resize, or rename parts in a VOCALOID6 project to adjust song structure and labels without manually editing individual events.

Instructions

Move, resize or rename 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": "edit_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
partYes
pathNo
trackYes
durationNo
positionNo

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, yet it discloses almost nothing beyond the operation list. It does not say whether omitted parameters leave values untouched (partial-update semantics), whether edits are persistent/undoable, what happens if track and the part's current track differ, or what is returned. For a mutation tool with zero annotation coverage this is a substantial gap.

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?

Two short sentences with the operation list front-loaded and no filler; the bilingual repetition is purposeful localization rather than waste. It is appropriately sized, though brevity here is achieved by omitting needed detail rather than by editing.

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 definition is too thin: it never explains the required track/part pair, the path parameter, or what an edit returns. The agent would have to guess at semantics that the schema does not supply.

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 six parameters, so the description must compensate. It only loosely maps three operations to three likely fields (rename→name, resize→duration, move→position) and says nothing about the required 'track' and 'part' identifiers or the unexplained 'path' parameter. Half the parameters remain semantically 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?

The description names a specific resource (a part) and enumerates concrete operations: move, resize, rename. This clearly separates it from siblings like add_part, remove_part, and fit_part, which are create/delete/fit operations. It stops short of explicitly naming those siblings as alternatives, but the verb+resource is unambiguous.

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 guidance on when to use this tool versus alternatives, nor preconditions such as whether a project must be open or whether the part must already exist. The agent must infer from the sibling names that creation goes to add_part and deletion to remove_part.

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