Skip to main content
Glama
Sign In
ableton-mcp-lofifren

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_scene_tempo

Assign a tempo to a scene. When the scene is triggered, the global song tempo changes to that value.

Instructions

Set a per-scene tempo. Firing this scene will set the song tempo to this value.

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

Input Schema

NameRequiredDescriptionDefault
scene_indexYes
tempoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses the effect on song tempo when scene fires, but does not mention persistence, precedence, or side effects.

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 concise sentences with no wasted words. Front-loaded with the key action.

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 simple 2-param tool with no output schema, description covers the main behavior. However, missing details like tempo units reduce completeness.

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

Parameters1/5

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

Description adds no meaning beyond schema. Schema coverage is 0%, yet description does not explain units, range, or format for scene_index or tempo (e.g., BPM).

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?

Description clearly states it sets a per-scene tempo and that firing the scene sets the song tempo. Distinguishes from sibling like set_tempo by specifying scene-level behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for scene-specific tempo control but does not explicitly state when to use versus global set_tempo or other tempo-related tools. No exclusions or alternatives mentioned.

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