Skip to main content
Glama

view

Read-only

Renders Blender scenes or images to a labeled PNG using multiple angles, shading modes, animation frames, or window/area screenshots, then restores temporary settings.

Instructions

One PNG of the scene + a caption line (which tile is which angle). width: pixels of the long side (of the whole image when combined). mode: viewport (windowed Blender: the user's view without the UI; background: the camera or an automatic frame), camera (at the render aspect), angles (frames the target from several directions; the background default), frames (an animation strip). shading: solid, texture, material, rendered (EEVEE), wireframe (edges over the surface), xray (transparent, bones visible). target: objects to frame, with their children (default everything visible; a big object such as a floor enlarges the frame). angles: at most 6 of front, back, left, right, top, bottom, iso or an [x, y, z] direction (default front, right, top, iso). distance: metres from the target to the eye. frames: frame numbers or frame_count (2-12, default 6); look: camera, an angle name or [x, y, z]; frames steps through the frames and returns to the old frame at the end. image: instead of the scene, 'Render Result', an open image name or a file path. area (windowed): 'window' = the whole window, 'NODE_EDITOR'/'OUTLINER'... = a screenshot of that area (the splash window may cover it); it cannot be combined with the other options. Temporary settings are restored.

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": {
      "app": "<app>"
    },
    "name": "view"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
areaNo
lookNo
modeNo
imageNo
widthNo
anglesNo
framesNo
targetNo
shadingNo
distanceNo
frame_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds substantial behavior: temporary settings are restored, frame stepping returns to the original frame at the end, the splash window may obscure an area capture, and a large object like a floor enlarges the frame. It also discloses the return shape (PNG plus caption) despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded first sentence is excellent, but the remainder is a dense semicolon-delimited wall of text with no grouping or line breaks, making it hard to scan for a specific parameter. Little is wasted, but the structure works against retrieval.

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?

For a 12-parameter, read-only capture tool with no output schema, the definition covers modes, shading, framing, return format, and state-restoration side effects. The remaining gaps are minor: the meaning of 'app' and whether/where the PNG is persisted are unstated.

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% across 12 parameters, so the description carries the full explanatory burden and largely succeeds: width, mode, shading, target, angles, distance, frames/frame_count, look, image, and area all get meaning, including value sets like the six angle names and the 2-12 frame count range. Only the required 'app' parameter is left unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states the concrete output — one PNG of the scene plus a caption line identifying each tile's angle — which is far more specific than the vague name 'view'. It does not, however, distinguish this from siblings such as 'scene' or 'open', leaving that differentiation to inference.

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?

Each mode is given a use condition: viewport for the user's own window without UI, camera at render aspect, angles as the background default, frames for an animation strip. It also states an exclusion ('area ... cannot be combined with the other options'), though it never says when to prefer this tool over a sibling tool outright.

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