Skip to main content
Glama

camera

Idempotent

Set a shot's viewpoint using a preset move with strength and wiggle, or direct it with timed keys; keys override the move.

Instructions

Set a shot's camera: a preset move with strength and wiggle, or direct it with camera keys (keys win over the move). Each key: at (seconds) and any of x, y, z, distance, height, angle, roll, ease; what a key leaves out is taken from where the camera is at that moment. Ids must come from the current style: call library to see them (a wrong id is refused with the valid list). Returns the camera settings. One undo step for the person. For the end-of-shot camera move into the next shot, use transition (outro_camera).

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

Input Schema

NameRequiredDescriptionDefault
keysNoCamera keys in time order.
moveNoCamera move id (library cameras). Clears camera keys.
shotNoThe shot's id (from get_project). Left out: the shot on screen.
wiggleNoHandheld feel: 0 locked off, 1 normal, up to 3.
strengthNoHow far the move goes, 0 to 100.
clear_keysNotrue: drop camera keys, back to the move.
replace_keysNofalse: add these keys to the ones there. Default replaces them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.1.2
    • addedInput schema / properties / keys / description
      Added value: +"Camera keys in time order."
    • addedInput schema / properties / keys / items / properties / angle / description
      Added value: +"Degrees around the point."
    • addedInput schema / properties / keys / items / properties / at / description
      Added value: +"Seconds into the shot."
    • addedInput schema / properties / keys / items / properties / distance / description
      Added value: +"Distance from that point, about 2 to 40."
    • addedInput schema / properties / keys / items / properties / height / description
      Added value: +"Camera height, about 0.3 to 30."
    • addedInput schema / properties / keys / items / properties / roll / description
      Added value: +"Tilt of the picture, about -3.2 to 3.2."
    • addedInput schema / properties / keys / items / properties / still / description
      Added value: +"true on a single key: a locked camera that doesn't move."
    • addedInput schema / properties / keys / items / properties / x / description
      Added value: +"Point it looks at: across."
    • addedInput schema / properties / keys / items / properties / y / description
      Added value: +"Point it looks at: height."
    • addedInput schema / properties / keys / items / properties / z / description
      Added value: +"Point it looks at: near (+) / far (-)."
    • changedInput schema / properties / move / description
      Previous value: -"Camera move id (clears camera keys)."New value: +"Camera move id (library cameras). Clears camera keys."
    • addedInput schema / properties / strength / description
      Added value: +"How far the move goes, 0 to 100."
    • addedInput schema / properties / wiggle / description
      Added value: +"Handheld feel: 0 locked off, 1 normal, up to 3."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare a non-readonly, idempotent, non-destructive write; the description adds the behavior an agent actually needs: missing key fields are inherited from the camera's current state, move clears keys, a wrong id is refused with the valid list returned, the call returns the camera settings, and there is exactly "one undo step for the person". That is substantive disclosure beyond the annotation set, with no contradiction.

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 two modes, then key semantics, id provenance, return value, undo cost, and the alternative — every sentence carries information. The style is telegraphic ("what a key leaves out is taken from where the camera is at that moment"), which is dense but slightly slows parsing of the inheritance rule.

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?

A 7-parameter mutation with no required fields and no output schema is well covered: it explains inheritance defaults, key replacement vs addition, clearing, return value, and undo granularity. The remaining gap is minor — it never states what the default shot target is, though the schema covers that for the `shot` property.

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 baseline is 3; the description earns an extra point by adding cross-parameter semantics the schema cannot express — keys winning over move, omitted key fields inheriting current camera position, and ids being constrained to the current style. It does not add per-parameter detail (ease values, ranges) beyond the schema, which is appropriate.

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 a shot's camera") and immediately splits it into its two operating modes: a preset "move" with strength/wiggle, or explicit "camera keys". It names the source of preset ids (library), the precedence rule ("keys win over the move"), and redirects the adjacent end-of-shot case to transition — an agent can distinguish this from `move`, `keys`, and `transition` without opening a 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 explicit routing for the most confusable alternative: "For the end-of-shot camera move into the next shot, use transition (outro_camera)", plus the internal rule that keys override a move. It also explains the id-provenance requirement (call library) and what happens on a bad id. It stops short of saying when to prefer keys over a move beyond the precedence note.

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