Skip to main content
Glama
Sign In
Ableton MCP

Ableton MCP

by Dysron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_groups

Retrieve all group tracks (folders) in your current Ableton Live session to organize and manage your project structure.

Instructions

List all group tracks (folders) in the current Live session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'List all group tracks' but doesn't describe return format, pagination, permissions needed, or potential side effects. For a read operation with zero annotation coverage, this is a significant gap in transparency, though it doesn't contradict any annotations.

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?

The description is a single, efficient sentence that front-loads the core action ('List all group tracks') and adds necessary context ('folders' clarification and 'in the current Live session'). There is zero waste, making it appropriately sized and well-structured for its 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?

Given the tool's simplicity (0 parameters, output schema exists, no annotations), the description is reasonably complete. It specifies what is listed and the context, though it could benefit from more behavioral details like return format. With an output schema handling return values, the description doesn't need to explain those, making it adequate for this low-complexity 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 has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description adds no parameter-specific information, which is appropriate here. Baseline for 0 parameters is 4, as no additional semantic detail is needed beyond what the schema provides.

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 clearly states the verb ('List') and resource ('group tracks (folders)'), specifying the scope ('in the current Live session'). It distinguishes from siblings like 'list_tracks' by focusing on groups/folders rather than individual tracks. However, it doesn't explicitly contrast with other group-related tools if any existed, keeping it from a perfect 5.

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?

The description implies usage when needing to see all group tracks in the current session, but provides no explicit guidance on when to use this versus alternatives like 'list_tracks' or 'find_track'. It lacks any 'when-not' scenarios or prerequisites, leaving usage contextually inferred rather than clearly defined.

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