Skip to main content
Glama

look

Read-onlyIdempotent

Capture a still frame from a shot or the whole film at a chosen time, with shot info, to review and fix your animation in the editor without changing the project.

Instructions

See a shot: returns a picture (about 960 px wide) of a shot at a moment, plus its info, so you can check what you made and fix it. Give a shot (id, or scene and shot index; default the shot on screen) and seconds into it, or film: true with seconds into the whole film. It shows that shot in the editor and pauses it; the project isn't changed. Doesn't work while a render runs. For the shot's settings as data use get_shot; for a video file use render.

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

Input Schema

NameRequiredDescriptionDefault
idNoA shot id (from get_project). Give this, or scene and shot. Left out: the shot on screen.
filmNotrue: seconds counts from the start of the whole film.
shotNoShot index in that scene, from 0.
sceneNoScene index from 0.
widthNoPicture width in pixels, 240 to 1920. Default 960.
formatNojpeg (default, smaller) or png.
secondsNoSeconds into the shot (or the film with film: true). Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / film / description
      Previous value: -"seconds counts from the start of the whole film."New value: +"true: seconds counts from the start of the whole film."
    • changedInput schema / properties / id / description
      Previous value: -"A shot id (from get_project)."New value: +"A shot id (from get_project). Give this, or scene and shot. Left out: the shot on screen."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, yet the description adds real behavioral context: the editor is shown the shot and playback pauses (a UI side effect not in annotations), the project is not changed, and a concurrent render blocks the call. These are the details an agent needs before invoking it mid-session.

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?

Purpose, then addressing modes, then behavioral caveats, then sibling routing — well front-loaded with no filler sentences. It is dense and slightly run-on in the middle clause, but every clause carries information.

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 7-optional-parameter read tool with no output schema, the description covers what comes back (a ~960px picture plus info), how to address the shot, and the runtime precondition. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3, but the description adds cross-parameter meaning the schema lacks: 'id, or scene and shot index' establishes the alternative addressing modes, the on-screen default, and 'film: true with seconds into the whole film' explains the film/seconds coupling. Only per-parameter ranges and enums (width, format) are left to the schema.

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?

Opens with a specific verb and resource ('See a shot') and immediately states the return ('returns a picture... of a shot at a moment, plus its info'). It explicitly separates itself from get_shot (settings as data) and render (video file), so an agent can pick it without opening sibling schemas.

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?

Gives the motivating use case ('so you can check what you made and fix it'), names two alternatives with the condition that selects each, and adds an explicit exclusion ('Doesn't work while a render runs'). Both when-to-use and when-not-to-use are covered.

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