Skip to main content
Glama

live12_song_get_state

Retrieves complete song and transport state from Ableton Live 12, including tempo, time signature, playing status, loop settings, scale, tuning, and track/scene counts.

Instructions

Reads comprehensive song and transport state from Ableton Live 12, including tempo, time signature, playing status, loop parameters, project musical scale, tuning system, and track/scene counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 behavioral burden. 'Reads' conveys a non-mutating operation, and the field list helps set expectations, but it does not explicitly state that the tool is side-effect-free, nor does it mention performance, caching, or any authorization requirements. Adequate but with clear gaps.

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?

A single, front-loaded sentence that wastes no words. The enumeration of fields is dense but purposeful and directly supports the agent's understanding of the return payload.

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?

There is no output schema, so the description must communicate what is returned. It does so by listing the key fields (tempo, time signature, playing status, loop parameters, scale, tuning system, track/scene counts), which is sufficient for an agent to decide whether to call it. It could be slightly richer about the response format, but it is largely complete for a zero-parameter read tool.

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?

The tool takes zero parameters, so parameter semantics are not a concern. The baseline for 0 params is 4, and the description does not need to explain parameters.

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 uses a specific verb ('Reads') and names the resource ('comprehensive song and transport state from Ableton Live 12'), then enumerates the exact fields returned. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling live12_lom_get, which may also read state.

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: an agent can infer this is the tool for inspecting song-level and transport-level state, especially given the many setter siblings like live12_transport_set_tempo. However, there is no explicit guidance on when to use this versus live12_lom_get or other getters, and no exclusions are stated.

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