Skip to main content
Glama
Sign In
ableton-mind

ableton-mind

by Pantani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_tempo

Set the global Ableton Live tempo in BPM (20-999). Changes are verified read-after-write, returning before/after values.

Instructions

Set the global Ableton Live tempo in BPM (20-999). Use for song-wide tempo changes before creating clips or scenes. Idempotent within 0.001 BPM and verified via read-after-write; returns before/after tempo and diff if verification disagrees.

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

NameRequiredDescriptionDefault
bpmYesTempo in BPM. Live's valid range: 20–999.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully shoulders transparency. It discloses idempotency within 0.001 BPM, read-after-write verification, and returned data (before/after tempo, diff on disagreement). This exceeds typical expectations.

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?

Two sentences efficiently cover purpose, range, usage context, and behavior. No superfluous words; front-loaded with the core action. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter, no output schema, and no annotations, the description is remarkably complete. It covers behavior, idempotency, verification, and return data. Minor gaps: no mention of error handling or side effects, but overall sufficient.

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?

Schema coverage is 100% with a clear description of the 'bpm' parameter. The description adds no parameter-level detail beyond what the schema already provides, so baseline 3 is appropriate.

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 the verb (Set), resource (global Ableton Live tempo), and scope (20-999 BPM). It distinguishes from sibling tools by specifying 'song-wide tempo changes before creating clips or scenes', and no other sibling tool handles tempo changes.

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

Usage Guidelines4/5

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

The description provides a clear use case ('use for song-wide tempo changes before creating clips or scenes') and implies safety via idempotency. However, it does not explicitly state when not to use or mention alternatives, which would elevate it to a 5.

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