Skip to main content
Glama

transition

Idempotent

Set how a shot changes into the next one: pick effect ID, length, options, or end-of-shot camera/effect/character moves and ready combos.

Instructions

Set how a shot changes into the next one: a transition id (cut, fade, whip-left, match-zoom-in, ink-splat... see library transitions), its length, and its options. Also the end-of-shot moves before it (outro camera, effect, character), or a ready combo of both. Empty string removes an outro part. Ids must come from the current style: call library to see them (a wrong id is refused with the valid list). Returns the transition. One undo step for the person.

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

Input Schema

NameRequiredDescriptionDefault
idNoTransition id (library transitions).
shotNoThe shot's id (from get_project). Left out: the shot on screen.
wordNoFor transitions that show a word.
colorNoFor transitions that use a colour: "#RRGGBB".
comboNoA ready-made combo id (outro + transition).
pointNoFor transitions that start at a point: [across, down], 0 to 1.
secondsNoTransition length in seconds.
outro_refNoWhich character id does the outro move.
outro_sizeNoSize of that character, 1 is normal.
outro_cameraNoOutro camera move id, or "" to remove.
outro_effectNoOutro effect id, or "" to remove.
outro_characterNoOutro character move id, or "" to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.1.2
    • addedInput schema / properties / color / description
      Added value: +"For transitions that use a colour: \"#RRGGBB\"."
    • changedInput schema / properties / id / description
      Previous value: -"Transition id."New value: +"Transition id (library transitions)."
    • addedInput schema / properties / outro_camera / description
      Added value: +"Outro camera move id, or \"\" to remove."
    • addedInput schema / properties / outro_character / description
      Added value: +"Outro character move id, or \"\" to remove."
    • addedInput schema / properties / outro_effect / description
      Added value: +"Outro effect id, or \"\" to remove."
    • addedInput schema / properties / outro_ref / description
      Added value: +"Which character id does the outro move."
    • addedInput schema / properties / outro_size / description
      Added value: +"Size of that character, 1 is normal."
    • addedInput schema / properties / point / description
      Added value: +"For transitions that start at a point: [across, down], 0 to 1."
    • addedInput schema / properties / seconds / description
      Added value: +"Transition length in seconds."
    • addedInput schema / properties / word / description
      Added value: +"For transitions that show a word."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive. The description adds real value beyond them: invalid ids are refused with the valid list, the call returns the transition, and it consumes one undo step for the person. That undo and validation behavior is not derivable from annotations.

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-loads the core action and packs the outro variant, id-sourcing rule, and undo note efficiently. It is dense and slightly run-on with parenthetical asides, but every sentence carries information.

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?

For a 12-parameter mutation tool with no output schema, the description covers the main modes (transition, outro moves, combo), the id-sourcing requirement, the return value, and the undo consequence. Only minor gaps remain, such as how combo interacts with individual fields.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all 12 parameters including the empty-string removal convention. The description restates the empty-string removal and points to library for ids, adding only marginal meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: 'Set how a shot changes into the next one' with a transition id, length, and options, plus the outro-move variant. An agent can distinguish this from siblings like camera or cut_shot without opening 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?

Gives a clear prerequisite: ids must come from the current style, and directs the agent to call library to see them, warning that a wrong id is refused with the valid list. It also explains that an empty string removes an outro part. It does not explicitly contrast with sibling tools such as camera, but the usage context is clear.

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