Skip to main content
Glama
Sign In
OpenUtau MCP

OpenUtau MCP

by Tehcnological
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fit_part

Resizes a voice part to end on the first bar line after its last note, aligning the part to bar boundaries.

Instructions

Resize a voice part to 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": {
      "part": "<part>"
    },
    "name": "fit_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 the deterministic rule governing the new part end (first bar line after the last note), which is genuine behavioral information. It does not say whether the operation is destructive to notes or events beyond that bar line, whether it can lengthen as well as shorten, or what it returns.

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?

The operative rule is front-loaded in one tight sentence with no filler. The full restatement in Japanese is duplicated content, which costs space but is a reasonable localization convention rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation tool with no annotations and no output schema, the description adequately explains what the transformation does. It is incomplete on the things an agent still needs: identifying the target part, the effect on material past the new endpoint, and the tool's result.

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% and the single parameter 'part' is documented only as an integer. The description mentions 'voice part' but adds no meaning: it does not clarify whether the value is an index or an ID, or where the agent obtains a valid part identifier. With low coverage the description needed to compensate and does not.

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 ('Resize a voice part') plus a precise outcome rule: end on the first bar line after the last note. That is far more informative than a tautology. It stops short of a 5 because it never distinguishes itself from the sibling 'ustx_fit_part', which an agent could easily confuse with this tool.

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 explicit when-to-use, when-not-to-use, or alternative guidance anywhere in the description. The purpose implies it is a length-normalization operation, but the agent must infer when fitting is preferable to editing notes or updating the part directly.

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

Deploy Server

Other Tools