Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_session_overviewB

Tempo, time signature, and summary of every track.

get_track_detailB

Devices, clip slots, and routing for one track.

get_clip_notesB

MIDI notes in a clip: pitch, start (beats), duration, velocity.

get_transport_stateB

Transport state: playing, current beat, loop.

get_selectedA

What the user currently has selected in Live. Call this first when the user asks 'what is this?'.

create_midi_clipC

Create a MIDI clip and fill with notes. Use this when the user wants a musical idea written into the set.

modify_clip_notesC

Replace all notes in an existing MIDI clip.

set_tempoC

Set song tempo (BPM).

set_time_signatureC

Set song time signature.

create_trackC

Create a new MIDI or audio track at end of set.

fire_clipA

Start playing a clip. ASK THE USER FIRST before calling — surprise playback is disruptive.

stop_clipC

Stop a clip.

explain_shortcutB

Look up an Ableton Live keyboard shortcut by action name.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 13 tools

Disambiguation5/5

Each tool targets a distinct action or resource: clip creation/modification, transport controls, track management, session overview, and shortcut lookup. No two tools have overlapping purposes.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern (e.g., create_midi_clip, get_clip_notes, set_tempo), making them predictable and easy to distinguish.

Tool Count5/5

13 tools cover the essential operations for an Ableton Live assistant without being overwhelming. The scope is well-balanced for core music production tasks.

Completeness4/5

Covers clip, track, transport, and session management. Missing operations like delete_track or record_arm are minor gaps that agents can work around, but core workflows are solid.

Maintenance

ActivityInactive
ResponsivenessNo issues