Skip to main content
Glama

fit_part

Aligns a VOCALOID part so it ends at the first bar line after its last note, matching part length to the bar grid.

Instructions

Make a part end on the first bar line after its last note. / パートを最後の音符の次の小節線までに合わせます

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

Input Schema

NameRequiredDescriptionDefault
partYes
pathNo
trackYes

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 states the resulting end position but not whether notes are moved, truncated, or preserved, whether the operation is undoable, or what happens to a part with no notes; for a mutation of part bounds that is a real 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?

A single front-loaded sentence stating the effect, with the Japanese rendering alongside it. Efficient, though the parallel bilingual text doubles length without adding information for an English-reading agent.

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 mutation tool with no annotations, no output schema, and zero schema parameter descriptions, the definition is thin: it lacks parameter meaning, prerequisites, side effects, and result information. The core effect is clear, but that is all that is complete.

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 three parameters, so the description must compensate and largely does not. It implies 'part' is the target but says nothing about how track and part together identify the target, and the 'path' parameter (a nullable string, presumably a project file) is left entirely unexplained.

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 verb+resource+effect: it makes a part end at the first bar line after its last note. That is concrete enough to distinguish it from generic siblings like edit_part or add_part. It stops short of 5 because it never explicitly contrasts itself with those siblings.

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 statement, no prerequisites (does the part need existing notes? must the project be open?), and no mention of the obvious alternative edit_part for changing part bounds. The use case is only inferable from the effect described.

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