Skip to main content
Glama
Sign In
OpenUtau MCP

OpenUtau MCP

by Tehcnological
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

seek

Move the playback cursor to a specified tick position, enabling playback or editing to start from an exact point in an OpenUtau project.

Instructions

Move the playback cursor. / 再生位置を移動します。

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": {
      "tick": "<tick>"
    },
    "name": "seek"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and delivers almost nothing beyond the verb. It does not say whether playback continues or starts after the seek, whether the tick is clamped to project length, or what happens if the target is out of range.

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?

The English sentence is front-loaded and efficient, but the Japanese line is a verbatim restatement rather than added information, which is filler for a machine reader. The definition is short yet under-specified rather than tight.

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 one-parameter transport tool with no annotations and no output schema, the description should at minimum cover tick semantics and the effect on playback state. Both are absent, so an agent cannot call it correctly without trial and error.

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 coverage is 0% for the single parameter, so the description must explain what a 'tick' means, whether the value is absolute or relative, and its relation to beats. It says none of this, leaving the agent to guess the unit even though a sibling (beats_to_ticks) implies a conversion exists.

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?

"Move the playback cursor" states a concrete verb and resource, which is enough to separate it from play/pause in the sibling list. It stops short of saying what the cursor is scoped to (a project, a track, a playing session), so the picture is clear but not fully pinned down.

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 call this rather than play, pause, or beats_to_ticks, and no stated preconditions such as an open project or active playback. The agent must infer that seeking is a positioning action separate from transport start/stop.

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