messier-live

by maramasaeva

Overview Schema Source Related Servers Discussions Admin

Python

Local

Set Tempo

set_tempo

Set the current Ableton Live session tempo to a specified BPM value to control playback speed across both decks.

Instructions

Set the session tempo in BPM.

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

Name	Required	Description	Default
`bpm`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

B3.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 burden of behavioral disclosure. It communicates that this is a mutating setter, but it does not mention side effects, valid tempo ranges, prerequisites, whether the change is immediate, or whether it affects playback.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundant words or filler. It states the action and target clearly and wastes no space.

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?

The tool is simple and has an output schema, so the description does not need to explain return values. Still, without annotations or parameter constraints, an agent may be uncertain about valid BPM values and the operational implications of changing the tempo.

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?

The schema only defines 'bpm' as a number with no description. The description adds semantic context by identifying it as 'session tempo in BPM', which clarifies the unit and role. However, it does not compensate for the lack of constraints such as accepted range, integer vs. decimal values, or rounding behavior.

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

Purpose5/5

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

The description clearly states a specific verb ('Set'), a resource ('session tempo'), and the unit ('BPM'). It is instantly distinguishable from the sibling tools, none of which handle session tempo.

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 usage guidance is provided: there is no mention of when to use this tool, when not to use it, or which alternative might be preferred. The intended use is only implicit from the name and description.

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