Skip to main content
Glama

set_song_scale

Sets Ableton Live 12's song scale so the piano roll displays it and scale-aware devices follow, with root and scale name mapping plus Scale Mode control.

Instructions

Set Live 12's song scale so the piano roll shows it and scale-aware devices follow it. scale accepts this server's names (dorian, hijaz, harmonic minor...) and maps them to Live's name when Live has the scale.

Parameters:

  • root: Tonic ("C", "Eb", "F#")

  • scale: Scale name

  • scale_mode: Turn Live's Scale Mode on/off

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_song_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNo
scaleNo
scale_modeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose meaningful traits: the change is visible in the piano roll, propagates to scale-aware devices, and scale names are translated to Live's naming with an acknowledged gap. It does not state what occurs when a scale name has no Live equivalent, whether the prior scale is restored, or whether the call can fail.

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 purpose sentence is front-loaded, and the parameter block is a tight three-line list with examples rather than prose. No sentence is redundant or wasted.

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?

An output schema exists, so return values need not be described, and the description covers the mutation's effect and all three parameters despite zero schema coverage. The remaining gap is edge-case behavior when a scale name is unmappable or when parameters are omitted.

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 description coverage is 0%, so the description must compensate, and it does document all three parameters with concrete examples ('C', 'Eb', 'F#' for root; dorian, hijaz, harmonic minor for scale) plus scale_mode's toggle meaning. However, all three parameters are optional with null defaults, and the description never says what an omitted parameter does or what the default state is.

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 names a specific verb and resource ('Set Live 12's song scale') and states the observable effect: the piano roll displays it and scale-aware devices follow it. It is clearly the write counterpart to the sibling get_song_scale, though it does not name that sibling explicitly.

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?

Usage is implied by the effect statement (call it when you want the piano roll and scale-aware devices to adopt a key), but there is no explicit when-to-use vs. when-not guidance and no prerequisites such as needing a Live 12 session. The caveat 'when Live has the scale' hints at a fallback path without saying what happens otherwise.

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