Skip to main content
Glama

stage_create_scene

Create a new 3D scene workspace for composition, supporting objects, lighting, camera shots, and physics bindings. Returns a scene ID for subsequent operations.

Instructions

Create a new 3D scene for composition.

Initializes a new scene workspace backed by chuk-artifacts.
The scene can contain 3D objects, lighting, camera shots, and physics bindings.

Args:
    name: Optional scene name (e.g., "pendulum-demo", "f1-silverstone-t1")
    author: Optional author name for metadata
    description: Optional scene description

Returns:
    CreateSceneResponse with scene_id and success message

Tips for LLMs:
    - Scene ID is auto-generated (UUID)
    - Scenes are stored in USER scope (Google Drive) if authenticated, SESSION scope otherwise
    - Use the scene_id for all subsequent operations
    - Typical workflow: create_scene → add_objects → add_shots → export

Example:
    scene = await stage_create_scene(
        name="falling-ball-demo",
        author="Claude",
        description="Simple gravity demonstration"
    )
    # Use scene.scene_id for next steps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
authorNo
descriptionNo
_user_idNo
Behavior4/5

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

With no annotations provided, the description discloses key behavioral traits: auto-generated scene ID (UUID), scope storage based on authentication, and that the tool is the first step in a workflow. It does not mention any destructive or side effects, but as a creation tool, the behavior is appropriately transparent.

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?

The description is well-structured with a concise headline, followed by detailed args, returns, tips, and an example. It is front-loaded with the key purpose and efficiently covers necessary information without unnecessary verbosity.

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?

Despite having no output schema, the description explains the return type (CreateSceneResponse with scene_id) and provides a complete workflow context. It covers scope, parameter use, and typical next steps, making it fully informative for an agent.

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 description coverage is 0%, but the description adds meaningful parameter guidance for name (with naming convention examples), author, and description. The parameter _user_id is not documented in the description, but the overall compensation for low schema coverage is strong.

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 tool's purpose: 'Create a new 3D scene for composition.' It specifies the resource (scene) and action (create), and distinguishes it from sibling tools like stage_add_object and stage_export_scene by focusing on initialization of a scene workspace.

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 description provides explicit workflow guidance ('Typical workflow: create_scene → add_objects → add_shots → export') and explains scope behavior (USER vs SESSION scope). It does not explicitly state when not to use this tool, but the context is clear enough for an agent to decide.

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