Skip to main content
Glama
Dorico Maestro

Dorico Maestro

rename_player

Idempotent

Rename a Dorico player by ID and return command completion status; it switches to Setup mode automatically because renaming is refused in Write mode.

Instructions

Rename a player by id.

Returns:
    Result dictionary with the command and whether Dorico finished it.

Note:
    Refused in Write mode, so this switches to Setup mode and back (Dorico
    Elements 6.2.40). No query lists players; their ids come from a saved project
    through read_playback_setup. Deleting a player by id is not possible: Dorico's
    command acts on the selection in Setup mode.

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": {
      "player": "<player>",
      "name": "<name>"
    },
    "name": "rename_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name.
playerYesPlayer id, see read_playback_setup.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.8

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, so an agent knows repeated calls are safe. The description adds genuinely useful non-obvious behavior: the hidden mode switch into Setup mode and back, the Write-mode refusal, and that the result reports whether Dorico finished. However, it does not disclose failure modes (e.g. what happens if the mode switch is blocked) or rate/state constraints beyond the mode note.

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 purpose is front-loaded in one sentence, then a returns section and a note section follow. The final sentence about deleting a player is tangential, explained as a limitation of Dorico's command rather than anything about this tool, but it does prevent a wrong-path attempt.

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 two-parameter rename command, everything an agent needs is in place: the purpose, the id source, the side effects of the Setup/Write mode switching, and a statement that the result reports completion. An output schema exists, so the extra returns note is a bonus rather than a gap-filler.

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?

Schema coverage is 100%, so both parameters are already documented, but the description adds the crucial provenance constraint that ids come only from a saved project via read_playback_setup. That constraint is not fully spelled out in the schema and meaningfully reduces the chance of an invalid id.

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 opening line states a specific verb plus resource plus the addressing key: "Rename a player by id." That is enough for an agent to distinguish it from siblings like read_playback_setup or activate_playback without consulting the schema.

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 gives real operating context: the tool is refused in Write mode so it self-switches to Setup mode and back, and player ids must be obtained from read_playback_setup because no query lists players. It stops short of explicitly naming an alternative tool to use instead or stating when a rename is preferable to other player operations, so it is clear context rather than full routing guidance.

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