Skip to main content
Glama
Sign In
Ableton MCP Extended

Ableton MCP Extended

by zabolotniydj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_scene

Add a new scene to the Ableton Live set at a specified index or append it at the end.

Instructions

Insert a new scene.

Parameters:

  • index: Position (1-based), or -1 to append at the end.

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

Input Schema

NameRequiredDescriptionDefault
indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It explains the key parameter's behavior (index position or -1 to append) which is a significant behavioral detail. It does not mention side effects or constraints like range checking, but for a create operation, this is sufficient.

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 very concise, with a clear one-line purpose and a bullet point for the parameter. No unnecessary text.

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?

The description provides the essential information needed for basic usage. It explains the parameter semantics and the default behavior. However, it does not mention any restrictions, effects, or when to use vs alternatives, but given the simple nature of the toolustom, it's adequate. Siblings give context.

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

Parameters5/5

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

The description clearly explains the only parameter 'index' with its meaning and special value -1, even though the schema doesn't provide description. This is explicit and unambiguous.

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 'Insert a new scene' with a specific verb and resource, and the parameter explanation distinguishes it from sibling tools like fire_scene or duplicate_scene. It is concise and unambiguous.

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?

The description gives clear context for when to use (creating a new scene) but does not explicitly mention when not to use or alternatives. However, the sibling tool names provide implicit differentiation, and the parameter guidance for index adds usage context.

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