Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

configure_camera

Adjust an existing Blender camera's lens, projection, clipping, sensor, depth of field, and location/rotation; optionally set it as the active scene camera.

Instructions

Configure properties and transform of an existing camera in the active Blender scene. Updates focal length (lens), projection type (PERSP, ORTHO, PANO), orthographic scale, clipping planes (clip_start, clip_end), sensor dimensions (sensor_width, sensor_height, sensor_fit), shift (shift_x, shift_y), depth of field (use_dof, focus_distance, aperture_fstop), 3D transform (location, rotation), and active camera assignment.

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

Input Schema

NameRequiredDescriptionDefault
dofNoDepth of field settings.
lensNoFocal length in millimeters (1.0 to 5000.0).
nameYesName of the existing camera object to configure.
typeNoAlias for camera projection type: 'PERSP', 'ORTHO', or 'PANO'.
shift_xNoHorizontal camera shift (-10.0 to 10.0).
shift_yNoVertical camera shift (-10.0 to 10.0).
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
use_dofNoEnable depth of field.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent. Mutations must be approved through a trusted approval mechanism.
clip_endNoFar clipping distance in Blender units (> clip_start).
locationNo3D world location coordinates [x, y, z].
clip_startNoNear clipping distance in Blender units (> 0.0001).
sensor_fitNoSensor fit mode: 'AUTO', 'HORIZONTAL', or 'VERTICAL'.
set_activeNoWhether to set this camera as the active scene camera.
camera_nameNoAlias for name of the camera object.
camera_typeNoCamera projection type: 'PERSP' (Perspective), 'ORTHO' (Orthographic), or 'PANO' (Panoramic).
ortho_scaleNoOrthographic scale factor for ORTHO cameras (> 0.001 to 10000.0).
target_nameNoAlias for name of the camera object.
focal_lengthNoFocal length in millimeters (alias for lens).
focus_objectNoTarget object name for dynamic depth-of-field focus point. Pass null or empty string to clear focus object.
sensor_widthNoCamera sensor width in millimeters (1.0 to 200.0).
sensor_heightNoCamera sensor height in millimeters (1.0 to 200.0).
aperture_fstopNoAperture f-stop number.
focus_distanceNoFocus distance in meters.
rotation_eulerNoEuler rotation angles in radians [rx, ry, rz].
track_to_objectNoTarget object name for camera to track using a TRACK_TO constraint. Pass null or empty string to remove tracking constraint.
show_composition_thirdsNoDisplay rule-of-thirds composition guide grid in the camera viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that this is a mutation of an existing object, but says nothing about what happens if the camera name is missing, how the three name aliases interact, whether updates are partial or full, or that approval must come from a trusted mechanism (the 'approved' param explicitly says client flags are untrusted).

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?

It is a single sentence, front-loaded with the intent and scope, which is good. But the long comma-separated enumeration of properties reads as a schema dump and does not prioritize or group what matters most.

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

Completeness2/5

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

With 27 parameters, nested DOF object, no annotations and no output schema, the description should do more. It omits alias handling, conflict resolution between duplicate parameters, tracking constraint behavior and the approval caveat, so an agent cannot fully call this correctly from the definition alone.

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

Parameters3/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 enumerates property groups that map onto parameters, but it ignores the most confusing schema feature: three name aliases (name/camera_name/target_name) and two lens aliases (lens/focal_length), plus a duplicated type/camera_type. Some listed concepts (track_to_object, show_composition_thirds, task_id, approved) get no mention at all.

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?

States a specific verb and resource ('Configure properties and transform of an existing camera in the active Blender scene') and the word 'existing' implicitly separates it from create_camera. It never names edit_camera or switch_camera, so distinction from the closest siblings is left 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. With siblings edit_camera, create_camera and switch_camera present, the definition gives no rule for choosing this tool over edit_camera or switch_camera, and no prerequisites such as the camera having to exist already.

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

Deploy Server

Other Tools