Skip to main content
Glama

Cutscene

Show a piece in a few versions

show_piece
Read-onlyIdempotent

Show the person a piece in Cutscene's window: playing in the film's brand, and 3 to 8 versions side by side (its settings, the scenes it dresses, another palette), each with « Essayer », then « Ajouter au film » and « Ouvrir dans l'éditeur », and its verdict in one line (« Prête », or « À corriger » with how many points: the points are yours, from create_piece and check_piece). Call it once a piece is written and checked, never at each writing. The answer also carries a contact sheet of the versions for you to look at, and says them in words for a host that draws no window: then ask the person which version, and put it in the film yourself with edit_film.

Input Schema

NameRequiredDescriptionDefault
atNoWhere « Ajouter au film » puts it: the scene before a join for a transition, the scene for an effect, an animation or a camera move, the place a scene takes. Left out: the first join or scene, or before the last scene
idYesThe piece: one of the user's own (create_piece), or of the library
langNoThe person's language, for the names in the answer and the example words of the versions (default: the film's, else en)
nameNoThe film it would go in (its id on the account, prj_…): the versions wear its brand and « Ajouter au film » puts it there

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description goes significantly beyond the boolean hints provided in annotations, detailing the entire UI interaction (Essayer, Ajouter au film, Ouvrir dans l'éditeur) and even providing instructions for non-window users (verbal description of versions).

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?

While slightly verbose, the tool's complexity necessitates the length. The structure prioritizes the unique selling point (multi-version display) before detailing the workflow and inputs.

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?

Given the tool involves a complex decision-making flow (verdict -> verbal description -> user choice -> edit_film), the description provides all necessary context for an agent to handle such a multi-step workflow request.

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?

Since schema coverage is 100%, the baseline is 3. The description still adds value by framing the parameters within the business logic (e.g., specifying that 'id' can be from creation or the library, and defining the specific context for 'at').

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 description clearly states the core function: displaying a piece along with 3 to 8 variants in a specific window. It distinguishes itself by detailing the visual presentation (side-by-side versions, verdicts) and workflow (Verdicts -> Ask -> edit_film).

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

Usage Guidelines5/5

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

It provides explicit timing guidance: 'Call it once a piece is written and checked, never at each writing.' This precisely defines the lifecycle stage when the tool is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources