Skip to main content
Glama

set_tempo

Change the song tempo in Ableton Live by specifying beats per minute (20–999), so AI assistants can set or adjust playback speed for composition and arrangement.

Instructions

Change the song tempo.

Parameters:

  • tempo: Beats per minute (Live accepts 20–999)

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

Input Schema

NameRequiredDescriptionDefault
tempoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description bears the full behavioral burden; it discloses the accepted BPM range (20–999) which is genuine behavioral context about valid input. However it says nothing about whether the change is immediate during playback, undoable, or project-scoped, which matters 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 lines, front-loaded with the action, then a compact parameter note. The "Parameters:" header for a single argument is slightly ceremonial but not wasteful.

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?

An output schema exists, so return values need not be explained, and the single parameter's units and range are covered. For a simple mutation tool, though, the absence of any note on effect timing or persistence leaves a modest gap.

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

Parameters4/5

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

Schema coverage is 0% (the schema only declares a bare number titled "Tempo"), so the description must compensate, and it does: it specifies units (beats per minute) and the valid range 20–999. That is a meaningful addition beyond the schema, though it could note whether decimals are honored.

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?

"Change the song tempo" gives a specific verb (change) plus resource (song tempo), which is unambiguous and distinguishes it from siblings like set_song_scale or set_arrangement_time. It stops short of explicitly naming the boundary with those siblings, so it is clear but not maximally differentiated.

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 versus alternative tempo-related tools, no stated prerequisites (e.g. whether playback must be stopped), and no exclusions. Usage is only implied by the tool name.

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