Skip to main content
Glama
Sign In
ableton-mcp

ableton-mcp

by jpoindexter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_scene_color

Fetch the color of a scene in Ableton Live using its scene index.

Instructions

Get the color of a scene.

Parameters:

  • scene_index: The index of the scene

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scene_index": "<scene_index>"
    },
    "name": "get_scene_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral transparency. It does not disclose the return format (e.g., RGB tuple, hex string), behavior for invalid scene_index, or potential errors, leaving the agent without critical operational details.

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?

The description is brief and front-loaded with the main purpose. However, the parameter section is redundant with the schema and adds no value, slightly reducing efficiency.

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

Completeness2/5

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

Although this is a simple tool, the absence of an output schema and any description of return value or error behavior leaves a significant gap. An agent cannot know what to expect from the call, making the description incomplete for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description's parameter section ('The index of the scene') merely restates the parameter name without adding semantic meaning. It doesn't explain indexing convention (e.g., zero-based), valid range, or relationship to scene list.

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 states the tool's function with a specific verb ('Get') and resource ('color of a scene'), clearly distinguishing it from sibling tools that operate on clips or tracks. However, it doesn't elaborate on what a 'scene' is or how color is represented.

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

Usage Guidelines2/5

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

No usage context is provided. The description doesn't indicate when to prefer this tool over related tools like get_all_scenes or set_scene_color, nor mention any prerequisites or alternative approaches.

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