Skip to main content
Glama

set_camera

Move the active viewport camera to a world point or frame a prim, setting position and target or orbiting by distance, azimuth, and elevation.

Instructions

Move the viewport's camera and aim it, at a world point or at a prim.

For a point, position is where the camera stands and target what it looks at, the world origin when left out. For a prim, prim_path, and the camera goes around the prim's centre at distance, azimuth and elevation, without position or target. It moves whichever camera the viewport looks through, a scene camera included, and the user sees the move. inspect_prim captures a prim from up to 14 sides in one call; capture_viewport's camera_path captures from another camera without moving the viewport. An error when the prim doesn't exist, when position is the point it would look at, and for a mix of the two forms, saying what to drop.

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

Input Schema

NameRequiredDescriptionDefault
targetNo[x, y, z] the world point it looks at, the world origin when left out: for a point
azimuthNoDegrees around the prim: 0 the front (+Y on a Z-up stage, +Z on a Y-up one), 90 the right (+X), 180 the back, 270 the left; 45 when left out
distanceNoFrom the prim's centre in stage units; 2.5 times its largest side when left out
positionNo[x, y, z] where the camera stands, in world space: for a point
elevationNoDegrees above the horizontal; 30 when left out
prim_pathNoA prim to frame instead: the camera aims at the centre of its world box

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.4.1
    • addedInput schema / properties / azimuth
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Degrees around the prim: 0 the front (+Y on a Z-up stage, +Z on a Y-up one), 90 the right (+X), 180 the back, 270 the left; 45 when left out",
      +  "title": "Azimuth"
      +}
    • addedInput schema / properties / distance
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "From the prim's centre in stage units; 2.5 times its largest side when left out",
      +  "title": "Distance"
      +}
    • addedInput schema / properties / elevation
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Degrees above the horizontal; 30 when left out",
      +  "title": "Elevation"
      +}
    • addedInput schema / properties / position / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "number"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / position / default
      Added value: +null
    • changedInput schema / properties / position / description
      Previous value: -"[x, y, z] camera position in world space"New value: +"[x, y, z] where the camera stands, in world space: for a point"
    • removedInput schema / properties / position / items
      Removed value: -{
      -  "type": "number"
      -}
    • removedInput schema / properties / position / type
      Removed value: -"array"
    • addedInput schema / properties / prim_path
      Added value: +{
      +  "default": "",
      +  "description": "A prim to frame instead: the camera aims at the centre of its world box",
      +  "title": "Prim Path",
      +  "type": "string"
      +}
    • changedInput schema / properties / target / description
      Previous value: -"[x, y, z] world point to look at; the origin when omitted"New value: +"[x, y, z] the world point it looks at, the world origin when left out: for a point"
    • removedInput schema / required
      Removed value: -[
      -  "position"
      -]
  2. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / target / description
      Previous value: -"[x, y, z] point to look at"New value: +"[x, y, z] world point to look at; the origin when omitted"
  3. First observedv0.2.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real behavioral context beyond that — it moves whichever camera the viewport looks through, including a scene camera, and the user visibly sees the move. It also enumerates the error conditions (missing prim, position equal to target, mixed forms). It stops short of saying whether the prior camera state is recoverable, which is the one remaining gap for a mutating tool.

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 core action, then two tight lines for the modes, then alternatives, then failure modes. Dense and useful throughout, though the closing clause 'saying what to drop' is slightly indirect phrasing for 'the error tells you which parameter set to drop'.

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 an output schema present, return values need no explanation, and the description covers mode selection, side effects, alternatives, and failure modes. For a 6-parameter all-optional camera tool, nothing an agent needs in order to call it correctly is missing.

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 100% and already documents defaults (45° azimuth, 30° elevation, 2.5× largest side, world origin), so the baseline is 3. The description adds semantics the schema does not encode: the two parameter sets are mutually exclusive and mixing them is an error, plus prim mode forbids position/target.

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 opening sentence names a specific verb and resource ('Move the viewport's camera and aim it') and immediately scopes the two targeting modes: a world point or a prim. That is enough for an agent to separate it from capture_viewport and inspect_prim without opening any schema.

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?

It states exactly when each form applies (position+target for a point; prim_path with distance/azimuth/elevation for a prim) and names the alternatives with the condition that selects them: inspect_prim for multi-side capture, capture_viewport's camera_path for capturing from another camera without moving the viewport.

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