Skip to main content
Glama

control_viewport

Control the live Blender GUI viewport by selecting or framing objects, setting views, orbiting, panning, zooming, and shading to inspect and position remote scenes.

Instructions

Control the live Blender GUI: select/frame objects, orbit, pan, zoom and shade.

Requires a GUI session. Rotation is XYZ Euler angles in degrees; target pans
the view center. Changes persist in the live viewport. Capture with viewport_screenshot
after this job succeeds. Software graphics rendering happens remotely.

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": {
      "session_id": "<session_id>"
    },
    "name": "control_viewport"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo
frameNo
selectNo
targetNo
shadingNo
distanceNo
overlaysNo
rotationNo
session_idYes
frame_selectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful traits: a live GUI session is required, viewport changes persist, rotation is XYZ Euler in degrees, target pans the view center, and rendering happens remotely via software graphics. It still omits what happens on invalid selections, job failure behavior, and whether the operation is synchronous or asynchronous beyond the reference to a succeeding job.

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 short, front-loaded with the main action, and each sentence conveys useful context such as the GUI requirement and screenshot follow-up. The line about software graphics rendering remotely is somewhat tangential but still adds operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with no annotations and no output schema, the description covers the environment requirement, persistence, and follow-up capture but leaves most parameter semantics and the result behavior unexplained. It is adequate to start using the tool but incomplete for reliably invoking all of its options.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, so the description must compensate. It explains only rotation (XYZ Euler degrees) and target (pans the view center), leaving view, frame, select, shading, distance, overlays, frame_selected, and session_id without semantic clarification beyond their names and types.

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 uses a specific verb and resource ("Control the live Blender GUI") and enumerates the concrete operations: select/frame objects, orbit, pan, zoom and shade. It also distinguishes itself from the sibling capture tool by directing the agent to viewport_screenshot for images rather than treating this as a screenshot tool.

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?

It states a prerequisite ("Requires a GUI session") and a clear follow-up workflow ("Capture with viewport_screenshot after this job succeeds"), which tells the agent when and how to sequence this tool. It does not state exclusions or failure conditions, so it stops short of full when/when-not guidance.

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