Skip to main content
Glama

get_session_snapshot

Capture a complete snapshot of the Live set, including tracks, mixer, devices, clips, scenes, returns and locators. Use it to compare the session before and after edits.

Instructions

Everything in the set at once: every track with its mixer, devices, Session and Arrangement clips, plus scenes, returns, the main track and locators. Handy to compare the set before and after a series of edits.

Parameters:

  • include_notes: Include the MIDI notes of every clip (default true)

  • include_params: Include every device parameter value (default true)

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_session_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_notesNo
include_paramsNo

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?

No annotations are supplied, so the description carries the full burden. It discloses the scope of what is read and, importantly, that include_notes/include_params default to true — meaning the call is expensive by default. What it omits is the practical consequence: payload size and latency for a full-set snapshot, and whether it is a pure read with no side effects.

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?

Two tight sentences up front followed by a compact parameter list; the scope statement is front-loaded. The parameter lines partially restate schema defaults, but since the schema has zero descriptions this redundancy is justified.

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 shape need not be described, and both parameters are documented despite 0% schema coverage. The remaining gap is behavioral rather than structural: no warning about the size/expense of a whole-set snapshot, which is the main risk for an agent invoking this.

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?

Schema description coverage is 0% (only bare titles 'Include Notes' / 'Include Params'), so the prose does real work: it clarifies that include_notes means MIDI notes of every clip and include_params means every device parameter value, both defaulting to true. That is meaningfully more than the schema conveys, short of explaining cost trade-offs.

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 concrete framing — 'Everything in the set at once' — and enumerates the resources returned (tracks, mixer, devices, clips, scenes, returns, main track, locators). This implicitly separates it from the granular siblings like get_track_info or get_session_info, though it never names one 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?

One usage scenario is given: 'Handy to compare the set before and after a series of edits.' That hints at when to reach for it, but there is no 'when not to use' guidance and no mention of the narrower getters (get_track_info, get_scenes, get_device_parameters) that an agent should prefer for targeted reads.

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