Skip to main content
Glama

inspect_prim

Captures a prim from up to 14 cube-face and corner angles, framed to fill each image, saving PNGs so you can review an object from every side.

Instructions

Capture a prim from up to 14 angles around it, each framed so the prim fills the image, and save each as a PNG in mcp_output/captures/.

Use it to see one object from every side; capture_viewport takes one picture from a camera as it stands. The angles are the 6 face centres and 8 corners of a cube around the prim, all 14 unless angles names some. The distance is fitted to the prim's size at width x height, then moved by zoom_offset. It moves whichever camera the viewport looks through, a scene camera included, and leaves it at the last angle. isolate hides everything but the prim and the lights while it captures, then shows them again. A call has about 80 s: an angle that fails says why, and the angles after it say Not captured. An orthographic camera is refused. An all-black angle, or lighting that lights nothing (mode off, or stage with no scene lights) though Kit's grid shows, comes with a warning, once a call, saying what to change with viewport_light.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prim_path": "<prim_path>"
    },
    "name": "inspect_prim"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNoImage width in pixels, up to 4096; the camera is rendered at this size
anglesNoAngle names, all 14 when omitted. Face centres: "front", "back", "right", "left", "top", "bottom". Cube corners: "top_front_right", "top_front_left", "top_back_right", "top_back_left", "bottom_front_right", "bottom_front_left", "bottom_back_right", "bottom_back_left"
heightNoImage height in pixels, up to 4096; the camera is rendered at this size
isolateNoHide everything else while capturing, then restore it
prim_pathYesFull USD path of the prim, e.g. "/World/Robot"
zoom_offsetNoAdjusts the fitted distance: negative closer, positive further (-0.3 is 30% closer)
include_segmentationNoAlso capture instance segmentation at each angle

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • changedInput schema / properties / height / description
      Previous value: -"Image height in pixels"New value: +"Image height in pixels, up to 4096; the camera is rendered at this size"
    • changedInput schema / properties / width / description
      Previous value: -"Image width in pixels"New value: +"Image width in pixels, up to 4096; the camera is rendered at this size"
  2. First observedv0.2.2

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the tool moves whichever camera the viewport looks through and leaves it at the last angle, that isolate hides then restores other objects, an ~80 s per-call budget, per-angle failure semantics ('an angle that fails says why, and the angles after it say Not captured'), and warning conditions for all-black angles. These are exactly the side effects and limits an agent needs before committing to a mutating capture.

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?

Purpose and output path are front-loaded, then usage, then mechanics, then failure behavior — a sensible order with little filler. It is dense and a couple of clauses (the warning-sentence detail) could be tightened, but nothing is redundant with the schema.

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?

For a 7-parameter capture tool with an output schema, this covers everything an agent needs: what is produced, where it lands, camera side effects, runtime budget, failure reporting, and refusal/warning conditions. Return-value details are correctly left to the output schema.

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 coverage is 100%, so the baseline is 3; the description still adds real meaning by tying width x height to the fitted framing distance and explaining how zoom_offset modifies that fit, plus the cube-geometry rationale behind the angle set. It stops short of syntax detail beyond what the schema already lists.

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?

States a specific verb and resource ('Capture a prim from up to 14 angles around it'), the framing rule, and the output location (PNG in mcp_output/captures/). It also explicitly contrasts itself with the nearest sibling, capture_viewport, so the agent can route between them without opening either 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?

Gives an explicit selection rule: 'Use it to see one object from every side; capture_viewport takes one picture from a camera as it stands.' It adds preconditions that change tool choice (an orthographic camera is refused) and points to viewport_light when lighting is wrong.

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