Skip to main content
Glama
Dorico Maestro

Dorico Maestro

activate_playback

Idempotent

Activates the open project for playback and checks current state first so an already active project is not deactivated.

Instructions

Activate the open project for playback, leaving an active project as it is.

Returns:
    Result dictionary with ``activated_for_playback`` read back afterwards.

Note:
    ``Play.ActivateProject`` toggles: sent to a project that is already active it
    deactivates it (Dorico Elements 6.2.40). This reads the state first and sends
    the command only when the project is not active.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.8

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the bar is lower, but the description adds real value by explaining why: the underlying Play.ActivateProject toggles and would deactivate an active project, so the tool reads state first and only sends when inactive. This discloses the specific failure mode being prevented — meaningful context beyond the annotations. It does not state what happens when no project is open, which keeps it from a 5.

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?

Front-loaded with the action and its scope, followed by clearly labelled Returns and Note blocks. Every sentence carries information; the 'Returns' section is slightly redundant given an output schema exists, but it is brief.

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?

Output schema exists so return values need not be spelled out, and the description nonetheless previews the activated_for_playback key. For a zero-parameter tool with a covered output schema, the main residual gap is error/no-project behavior.

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 is 4. There is nothing for the description to disambiguate, and it correctly avoids padding with parameter prose.

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 a specific verb and resource — 'Activate the open project for playback' — and immediately qualifies the scope with 'leaving an active project as it is'. That is enough to distinguish it from near-neighbours like playback_state or playback_setup, although no sibling is named explicitly.

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 'leaving an active project as it is' clause implies the safe/idempotent calling context, and the Note explains the guarded behavior. However, there is no explicit statement of when to prefer this over playback, playback_setup, or playback_state, and no prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.