Skip to main content
Glama

fire_scene

Launch all clips in a specified scene row to trigger a full section in Ableton Live.

Instructions

Launch every clip in a scene's row.

Parameters:

  • scene_index: The scene to launch

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

Input Schema

NameRequiredDescriptionDefault
scene_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says clips are launched but not whether this starts transport, applies launch quantization, stops other playing scenes, is reversible, or errors when the scene is empty — all material for a playback-triggering mutation.

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?

A single purpose sentence followed by a short labeled parameter block; it is front-loaded and free of filler. The brevity is appropriate in form, though the small budget is spent poorly given the missing behavioral detail.

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?

An output schema exists, so return values need not be explained. But for a transport-affecting trigger with zero annotation coverage and an undocumented index parameter, the description leaves the agent without the essentials needed to call it correctly.

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

Parameters2/5

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

Schema coverage is 0% for the single required parameter, and the description only restates it as 'the scene to launch.' It never specifies whether scene_index is zero-based or one-based, its valid range, or what happens with an out-of-range value — exactly the ambiguity that causes wrong invocations.

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?

Names a specific verb and resource: 'Launch every clip in a scene's row.' An agent can distinguish this bulk scene-level action from the clip-level fire_clip sibling by inference from the wording. It stops short of explicitly contrasting the two, which keeps it out of 5 territory.

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?

There is no statement of when to use this versus fire_clip, no preconditions (e.g., whether the scene must exist or be selected), and no note on what happens to already-playing clips. The agent must infer selection criteria entirely from the name and one-line purpose.

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