Skip to main content
Glama

live_status

Read-onlyIdempotent

Check whether Ableton Live is connected and inspect the open Set's tempo, time signature, track counts, and scenes; use it to diagnose connection errors and get setup details.

Instructions

Check the connection to Ableton Live and show the open Set.

Returns whether Live is connected, the Live and Tonable versions, and the Set's tempo, time signature and numbers of tracks, return tracks and scenes. When Live is not reachable it returns connected=false with the reason and what to do. Use it first in a conversation and after any connection error.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by defining the failure contract: connected=false with the reason and a suggested remedy. It says nothing further about latency, timeouts, or whether the call retries.

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?

Four short sentences, front-loaded with the core action, then the return payload, then the failure case, then the usage rule. No redundant restatement of the title or annotations.

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?

With no output schema, the description carries the return-value burden and does so by listing the returned fields and the disconnected-case shape. The remaining gap is structural detail (nesting of the version or Set fields), which keeps it just short of fully 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?

The tool takes no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly spends no words on inputs.

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?

States a specific verb and resource: check the connection to Ableton Live and show the open Set. It then enumerates exactly what is reported (connected flag, Live/Tonable versions, tempo, time signature, track/return-track/scene counts), which lets an agent separate this diagnostic tool from set-reading siblings.

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?

Gives two concrete conditions for use: first in a conversation, and after any connection error. That is clear positive guidance. It stops short of naming when-not to use it or which sibling to call instead, so it is not a full when/when-not/alternatives statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.