Skip to main content
Glama

get_groove_pool

Retrieves the grooves loaded in the current Ableton Live set, including per-groove timing, random, velocity, quantization amounts, and the global groove amount.

Instructions

Live's Groove Pool: the grooves loaded in the set (name, base, timing, random, velocity and quantization amounts) and the global Groove amount. Grooves live in the browser under Packs (e.g. get_browser_items_at_path("packs/Core Library/Grooves")) and in the User Library; apply one with set_clip_groove. A groove only acts when the global amount is above 0 (set_groove_params global_amount).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/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 behavioral burden. It does disclose one genuinely useful trait beyond structure: grooves are inert unless the global amount is above 0, which affects how an agent interprets results. However, it never states read-only/no-side-effect behavior explicitly, nor what happens when the pool is empty or unloaded, leaving parts of the behavior to inference from the 'get_' prefix.

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?

Front-loaded with the resource identity and contents, then followed by provenance, the apply path, and the gating condition. No sentence is padding; the parenthetical field list is dense but serves as the payload summary. It is compact for the amount of routing information delivered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless getter with an output schema already defining return values, the description covers everything an agent needs to decide to call it and to make sense of what it sees: what is returned, where grooves originate, how to apply one, and why a groove may appear to have no effect. No significant gap remains.

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 zero parameters, so the baseline of 4 applies. The description instead characterizes the returned record shape (the per-groove amounts and the global amount), which usefully primes the agent on what the output contains without pretending to document inputs.

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 names the resource precisely: 'Live's Groove Pool: the grooves loaded in the set' plus the enumerated fields (name, base, timing, random, velocity, quantization amounts) and the global Groove amount. The retrieval verb is only implicit, but the returned data is unambiguous. It also distinguishes itself from the write-side siblings (set_clip_groove, set_groove_params) by describing them as the actions this getter supports.

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?

It tells the agent how this fits into a workflow: grooves are loaded from the browser under Packs (with a concrete example path) or the User Library, and are applied via set_clip_groove. It also gives the critical precondition that a groove only acts when the global amount is above 0, pointing at set_groove_params. It stops short of an explicit 'call this when you want to inspect...' statement or a when-not-to-use caveat.

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