ableton-mind

Overview Schema Source Related Servers Discussions Admin

session_snapshot

Take a read-only snapshot of the Live session to verify changes with session_diff. Returns tracks and optional clips or devices without affecting playback.

Instructions

Read-only deep snapshot of the Live session. Use before and after mutating tools to verify changes with session_diff; returns tracks and optional clips/devices without changing playback or session state.

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

Input Schema

Name	Required	Description	Default
`include_clips`	No
`include_devices`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It clearly labels the tool as 'read-only' and 'deep snapshot' and explicitly states it does not change playback or session state, giving agents confidence in its safety.

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?

Two sentences with no wasted words. Purpose, usage guidance, and behavioral traits are front-loaded. Every sentence serves a purpose.

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?

No output schema, yet description gives a high-level idea of what is returned ('tracks and optional clips/devices'). For a snapshot tool with two optional booleans, the description is mostly complete. Lacks details on return format, but not critical for an agent.

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

Parameters3/5

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

Schema description coverage is 0%, so description must compensate. It mentions 'optional clips/devices', hinting at the two boolean params (include_clips, include_devices), but does not explicitly name them or explain their effect in detail. Adds some meaning but could be clearer.

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?

The description clearly states 'Read-only deep snapshot of the Live session' and specifies the returned data ('tracks and optional clips/devices'). It distinguishes from siblings like 'session_diff' by positioning itself as the data capture tool used before and after mutations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use before and after mutating tools to verify changes with session_diff', providing a clear usage context and alternative. Also notes it does not change state, so it's safe to call without side effects.

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