Skip to main content
Glama

set_tempo

Sets the tempo in BPM at a specified tick position, or applies a song-wide tempo when position is 0, to control timing in VOCALOID6 projects.

Instructions

Set the tempo at a tick (0 = song tempo). / 指定ティックのテンポを設定します(0 = 曲全体)

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": {
      "bpm": "<bpm>"
    },
    "name": "set_tempo"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmYes
pathNo
positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/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. It does not say whether an existing tempo at that tick is overwritten, whether the change is undoable, what permissions or project state are required, or what happens on an invalid tick — all material for a mutation tool.

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 core action and the key value convention front-loaded; nothing is padded. The English/Japanese duplication adds length without adding information, which keeps it from a 5.

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 0% schema coverage, the description is thin. The unexplained `path` parameter and the absence of any statement about overwrite behavior or required project context leave an agent guessing before invocation.

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

Parameters3/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. It does clarify the position semantics (tick-based, 0 = song tempo), but bpm is only inferable from its name and the `path` parameter is never explained at all, leaving a real gap.

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 ("Set the tempo") plus the scope qualifier "at a tick (0 = song tempo)", which lets an agent distinguish it from remove_tempo. It stops short of naming any sibling or contrasting behavior explicitly.

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?

No guidance on when to use this versus remove_tempo or set_time_signature, and no prerequisites such as requiring an open project. The only usage hint is the parenthetical that 0 means song-wide tempo, which is a value convention rather than a when-to-use rule.

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