Skip to main content
Glama
FreeRiverHouse

AbletonMCP

by FreeRiverHouse
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

set_tempo

Adjust the tempo of your Ableton Live session by specifying a new BPM value to control playback speed and timing.

Instructions

Set the tempo of the Ableton session.

Parameters:

  • tempo: The new tempo in BPM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tempoYes

Implementation Reference

  • AbletonMCP_Remote_Script/__init__.py:553-564 (handler)
    The actual implementation of set_tempo that interacts with the Ableton Live song object.
    def _set_tempo(self, tempo):
    """Set the tempo of the session"""
    try:
        self._song.tempo = tempo
        
        result = {
            "tempo": self._song.tempo
        }
        return result
    except Exception as e:
        self.log_message("Error setting tempo: " + str(e))
        raise
  • MCP_Server/server.py:347-358 (handler)
    The MCP tool handler that receives the request and calls the _run helper.
    def set_tempo(ctx: Context, tempo: float) -> str:
    """
    Set the tempo of the Ableton session.

    Parameters:
    - tempo: The new tempo in BPM
    """
    try:
        _run("set_tempo", {"tempo": tempo})
        return f"Tempo set to {tempo} BPM"
    except Exception as e:
        return f"Error setting tempo: {e}"

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it 'sets' tempo (implying mutation) but doesn't disclose effects (e.g., immediate change, session save state), permissions needed, or error conditions. This leaves significant gaps 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?

The description is appropriately brief with two sentences: one stating the purpose and another listing parameters. There's no wasted text, though the parameter formatting is slightly verbose for a single parameter. It's effectively front-loaded with the core action.

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 no annotations and no output schema, the description is incomplete. It lacks crucial context like valid tempo ranges, whether changes persist, error handling, or confirmation of success. Given the complexity of modifying a live session, this leaves the agent under-informed.

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 description adds basic semantics by explaining 'tempo' as 'The new tempo in BPM', which clarifies the unit beyond the schema's generic 'number' type. However, with 0% schema description coverage and only 1 parameter, this minimal addition meets but doesn't exceed baseline expectations for such a simple tool.

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 description clearly states the action ('Set') and the target resource ('tempo of the Ableton session'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'start_playback' or 'stop_playback' that also affect session timing, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether Ableton must be running), constraints (e.g., valid tempo ranges), or related tools like 'get_session_info' that might provide current tempo context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FreeRiverHouse/ableton-flow'

If you have feedback or need assistance with the MCP directory API, please join our Discord server