Skip to main content
Glama

get_song_scale

Retrieves Live 12's song scale: root, scale name, intervals, and Scale Mode switch. Use it to check which scale is active for piano-roll highlighting and devices set to Use Current Scale.

Instructions

Live 12's song scale: root, scale name, intervals and the Scale Mode switch (which highlights the scale in the piano roll and drives devices set to "Use Current Scale", e.g. the Scale, Arpeggiator and Chord devices).

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": "get_song_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 carries the full disclosure burden. It does add genuinely useful behavior beyond the schema by explaining that Scale Mode highlights the scale in the piano roll and drives devices bound to "Use Current Scale" (Scale, Arpeggiator, Chord), but it never states that the call is read-only and side-effect free, which is the key safety fact an agent needs.

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?

A single front-loaded sentence that identifies the resource first and then enumerates the returned fields. The trailing parenthetical about driving devices is long but earns its place by explaining Scale Mode semantics; the phrasing is slightly compressed into one breath rather than structured.

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 spelled out, and the description correctly focuses on the non-obvious semantic layer (what Scale Mode actually affects). What remains missing is the read-only confirmation and any pointer to set_song_scale, but for a zero-argument getter this is close to complete.

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

Parameters4/5

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

Zero parameters, so there is nothing to disambiguate and the baseline is high. The description instead spends its words on output meaning, which is appropriate here.

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?

Names the exact resource (Live's song scale) and enumerates what it reports: root, scale name, intervals, and the Scale Mode switch. The read intent is only implied by the leading noun phrase rather than an explicit verb, and it never contrasts itself with the sibling set_song_scale, so it falls short of full sibling differentiation.

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 only implied: an agent can infer this is the read path and set_song_scale is the write path, but the description never states when to call it or when to prefer the alternative. No exclusions or preconditions are given.

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