Skip to main content
Glama

remove_tempo

Deletes a tempo change at a specified position in a VOCALOID project to correct timing or remove an unwanted tempo event.

Instructions

Remove a tempo change. / テンポ変更を削除します

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": {
      "position": "<position>"
    },
    "name": "remove_tempo"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals only that the operation is destructive ("Remove"); it says nothing about whether later tempo changes shift, what happens if no tempo exists at the given position, or whether the change is undoable.

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 definition is a single front-loaded sentence with no padding. The bilingual repetition adds no information for an agent but consumes little space, leaving the wording essentially efficient.

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 zero annotations, no output schema, and two entirely undocumented parameters, the description is far short of what an agent needs. It states the operation but omits target identification, side effects, and failure conditions.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does not: neither the required `position` (which tempo event to target and what unit it uses) nor the optional `path` (which project/file is affected) is explained anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Remove a tempo change" supplies a specific verb and resource, so an agent knows the operation involves deleting a tempo event rather than a note or part. However, it is essentially an expansion of the tool name with no differentiation from the obvious counterpart set_tempo, and no statement about scope (single event vs. all tempo changes).

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 or when-not-to-use guidance, and the description never mentions set_tempo as the counterpart for adding/changing tempo. The agent must infer that this tool is for deletion only from the verb in the name.

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