Skip to main content
Glama

stage_add_object

Add 3D objects such as boxes, spheres, cylinders, and mesh placeholders to a scene, configuring their position, rotation, scale, and material for physics-based animations.

Instructions

Add a 3D object to the scene.

Adds primitives (box, sphere, cylinder, etc.) or placeholders for meshes.
Objects can be bound to physics bodies later for animation.

Args:
    scene_id: Scene identifier
    object_id: Unique object name (e.g., "ground", "ball", "car")
    object_type: Object type - "box", "sphere", "cylinder", "capsule", "plane", "mesh"
    position_x, position_y, position_z: Position in 3D space
    rotation_x, rotation_y, rotation_z, rotation_w: Rotation quaternion
    scale_x, scale_y, scale_z: Scale factors
    size_x, size_y, size_z: Size for box (width, height, depth)
    radius: Radius for sphere/cylinder/capsule
    height: Height for cylinder/capsule
    material_preset: Material preset - "metal-dark", "glass-blue", "plastic-white", etc.
    color_r, color_g, color_b: RGB color (0.0-1.0)

Returns:
    AddObjectResponse with object_id confirmation

Tips for LLMs:
    - For ground: object_type="plane", large size, static
    - For dynamic objects: smaller primitives that match physics bodies
    - Quaternion: [0,0,0,1] is identity (no rotation)
    - Common materials: "metal-dark", "glass-blue", "plastic-white", "rubber-black"

Example:
    # Add ground plane
    await stage_add_object(
        scene_id=scene_id,
        object_id="ground",
        object_type="plane",
        size_x=20.0,
        size_y=20.0,
        material_preset="metal-dark"
    )

    # Add falling sphere
    await stage_add_object(
        scene_id=scene_id,
        object_id="ball",
        object_type="sphere",
        radius=1.0,
        position_y=5.0,
        material_preset="glass-blue",
        color_r=0.3,
        color_g=0.5,
        color_b=1.0
    )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_idYes
object_idYes
object_typeYes
position_xNo
position_yNo
position_zNo
rotation_xNo
rotation_yNo
rotation_zNo
rotation_wNo
scale_xNo
scale_yNo
scale_zNo
size_xNo
size_yNo
size_zNo
radiusNo
heightNo
material_presetNoplastic-white
color_rNo
color_gNo
color_bNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses behavior (adds primitives/placeholders, can be bound to physics) and the return type (AddObjectResponse). However, it lacks details on permissions, side effects, or constraints like scene existence.

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 lengthy but well-structured with sections: general description, Args, Returns, Tips, and Example. It is comprehensive but could be more concise. However, the structure aids readability.

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?

Given 22 parameters, no output schema, and no annotations, the description is highly complete. It explains each parameter, provides common use-case tips, and includes two examples covering key object types (plane and sphere).

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%, so the description must compensate. It fully documents all 22 parameters with explanations, defaults, and relationships (e.g., radius for sphere/cylinder). This adds significant value beyond the bare 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?

The description clearly states it adds a 3D object to the scene, specifying primitives or placeholders. It distinguishes from siblings like 'stage_add_shot' and 'stage_create_scene' by focusing on object addition within a scene.

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 tips for LLMs, including typical objects like ground planes and dynamic spheres, and common material presets. It does not explicitly state when not to use or list alternatives, but the tips offer clear usage context.

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