Skip to main content
Glama

get_shot

Read-onlyIdempotent

Read every setting of a single shot as JSON—place, cast, actions, camera, lighting, and IDs—to inspect exact fields before editing the project or keys.

Instructions

Read-only: every setting of one shot as JSON (place, cast, actions, emotions, texts, camera and camera keys, lighting, transition, keyframes), with its scene and shot index. Use it to see exact fields and ids before edit_project or keys. For a short view of all shots use get_project; to see the shot as a picture use look.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe shot's id from get_project. Give this, or scene and shot. Left out: the shot on screen.
shotNoShot index from 0 inside that scene (used with scene).
sceneNoScene index from 0 (used with shot).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / id / description
      Added value: +"The shot's id from get_project. Give this, or scene and shot. Left out: the shot on screen."
    • addedInput schema / properties / scene / description
      Added value: +"Scene index from 0 (used with shot)."
    • addedInput schema / properties / shot / description
      Added value: +"Shot index from 0 inside that scene (used with scene)."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, and the description adds that the payload is a complete settings dump including scene/shot index — useful context beyond the flags. It does not address failure behavior (e.g., unknown id) or payload size, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: read-only scope and returned fields first, then when to use, then the two alternatives. Every sentence carries distinct information with no filler.

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?

With no output schema, the description carries the burden of describing the return value and does so by enumerating the included settings. Combined with the fully documented parameters and explicit alternatives, an agent has everything needed to call it correctly.

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% and the parameter descriptions already explain id vs scene+shot pairing and the 'shot on screen' default. The description adds no further parameter semantics, so the 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?

Names a precise operation ('Read-only: every setting of one shot as JSON') and enumerates the contents returned (place, cast, actions, emotions, texts, camera keys, lighting, transition, keyframes) plus scene and shot index. This clearly distinguishes it from get_project (summary of all shots) and look (rendered picture).

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 an explicit use case ('see exact fields and ids before edit_project or keys') and names two alternatives with the conditions that select them: get_project for a short view of all shots, look for a picture. Nothing is left to inference.

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