Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

set_time_signature

Idempotent

Insert a time signature change point into an Ardour session's tempo map at a specified musical or time position.

Instructions

Insert a time signature point through TempoMap.

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": {
      "request": "<request>"
    },
    "name": "set_time_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successNo
warningsNo
revision_afterNo
changed_objectsNo
revision_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation-and-safety profile is covered. The description adds nothing beyond that: it does not explain the dry_run, confirm_delete, or expected_revision semantics visible in the schema, nor what happens to a conflicting existing time signature.

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?

It is a single front-loaded sentence with no filler, which is structurally sound. But brevity here comes at the cost of under-specification rather than efficiency — there is only one clause of actual content.

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?

An output schema exists, so return values need not be described. Still, for a mutation tool with dry-run, delete-confirmation, and optimistic-revision parameters, the description should say something about conflict handling and the effect on existing time signature points; it does not.

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?

The single request parameter is a Meter object with a polymorphic position union (bbt/samples/seconds/quarter_ticks), plus dry_run, confirm_delete, and expected_revision fields, and schema description coverage is 0%. The description explains none of these, so it fails to compensate for the coverage gap.

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?

The description does supply a verb ('Insert') and a resource ('time signature point'), which distinguishes it from siblings like set_tempo or set_loop. However, 'through TempoMap' is internal jargon rather than user-facing scope, and it never states whether an existing point at the same position is replaced, which is the key behavioral question for a 'set_'-named 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 guidance on when to use this rather than set_tempo or the other set_* siblings, no prerequisites, and no note on whether the caller should already know the tempo map state. The agent must infer the entire usage context from the name.

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