Skip to main content
Glama

set_time_signature

Sets the time signature for a specific bar using numerator and denominator values, enabling precise musical meter changes in a VOCALOID project.

Instructions

Set the time signature from a bar (0-based). / 指定小節(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": {
      "numer": "<numer>",
      "denom": "<denom>"
    },
    "name": "set_time_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
barNo
pathNo
denomYes
numerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the definition carries the full burden of behavioral disclosure. It does not state that this is a mutation, whether it requires an open project or a valid path, whether the change applies to the remainder of the piece, or whether it is reversible. Only the 0-based bar convention is disclosed.

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 two short parallel sentences (English and Japanese) with no filler, and the 0-based convention is front-loaded. It is appropriately sized, though the bilingual duplication adds no information for an English-reading agent.

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 four-parameter mutation with no annotations, no output schema, and no parameter documentation, the definition is too thin. The missing 'path' semantics and the absence of any project-state prerequisite are the significant gaps; what is present is accurate but incomplete.

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%, so the definition must compensate and does not. 'bar (0-based)' is the only parameter meaning explained; 'numer' and 'denom' are never identified as the time signature's numerator and denominator, and 'path' (nullable, defaulting to null) is completely unexplained — the reader cannot tell whether it selects the target file or the current project.

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 definition states a concrete verb and resource ('Set the time signature') and adds a useful scope detail: it starts from a 0-based bar. It does not need to be distinguished from a close sibling because no other time-signature tool is listed, but it also does not say what numer/denom represent or how this interacts with existing bars.

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 about when to use this tool, what must already exist (an open project or a specific part path), or what happens to bars after the target bar. The reader must infer all prerequisites from the name and parameters alone.

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