Skip to main content
Glama

stage_add_shot

Define camera movement paths and time ranges for cinematography in 3D scenes, supporting orbit, static, chase, and other modes.

Instructions

Add a camera shot to the scene.

Defines a camera movement path and time range for cinematography.

Args:
    scene_id: Scene identifier
    shot_id: Unique shot name (e.g., "intro-orbit", "close-up")
    camera_mode: "orbit", "static", "chase", "dolly", "flythrough", "crane", "track"
    start_time: Shot start time in seconds
    end_time: Shot end time in seconds
    focus_object: Object ID to focus on (for orbit/chase modes)
    orbit_radius: Distance from focus object (orbit mode)
    orbit_elevation: Camera elevation angle in degrees (orbit mode)
    orbit_speed: Rotation speed in revolutions per second (orbit mode)
    static_position_x, static_position_y, static_position_z: Camera position (static mode)
    look_at_x, look_at_y, look_at_z: Point to look at
    easing: Easing function - "linear", "ease-in-out", "spring", etc.

Returns:
    AddShotResponse with shot details

Tips for LLMs:
    - Orbit mode: Great for product shots, object inspection
    - Static mode: Fixed camera, good for observing motion
    - Chase mode: Follow moving objects
    - Multiple shots can be sequenced for different camera angles

Example:
    # Orbiting shot around falling ball
    await stage_add_shot(
        scene_id=scene_id,
        shot_id="orbit-shot",
        camera_mode="orbit",
        focus_object="ball",
        orbit_radius=8.0,
        orbit_elevation=30.0,
        orbit_speed=0.1,
        start_time=0.0,
        end_time=10.0
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_idYes
shot_idYes
camera_modeYes
start_timeYes
end_timeYes
focus_objectNo
orbit_radiusNo
orbit_elevationNo
orbit_speedNo
static_position_xNo
static_position_yNo
static_position_zNo
look_at_xNo
look_at_yNo
look_at_zNo
easingNoease-in-out-cubic
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains parameters and camera modes but does not disclose error handling, side effects (e.g., appending shots), or prerequisites. The behavioral impact is partially inferred but not explicitly stated.

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?

The description is well-structured with summary, Args, Tips, and Example. Each section adds value without redundancy. The Tips section is particularly helpful. A slight reduction in length could be achieved, but overall it is appropriately concise.

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?

Given 16 parameters, no output schema, and no annotations, the description covers parameter semantics and usage tips well, including an example. It mentions the return type 'AddShotResponse with shot details'. It lacks details on potential errors or behavior under edge cases, but is fairly complete.

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

Parameters5/5

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

Schema description coverage is 0%, but the description includes a detailed Args list explaining each parameter's purpose, examples, and defaults (e.g., easing default 'ease-in-out-cubic'). This adds significant meaning beyond the schema's type and required fields.

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 'Add a camera shot to the scene' with specific verb 'Add' and resource 'shot'. It details the functionality (defines camera movement path and time range) and distinguishes from sibling tools like stage_get_shot.

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?

The 'Tips for LLMs' section provides explicit guidance on when to use each camera mode (e.g., orbit for product shots, chase for moving objects). It also mentions sequencing multiple shots. However, it does not explicitly compare to sibling tools or state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrishayuk/chuk-mcp-stage'

If you have feedback or need assistance with the MCP directory API, please join our Discord server