Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

switch_camera

Set an existing camera object as the active Blender scene camera. Validates the target exists and is type CAMERA before updating scene.camera.

Instructions

Switch the active scene camera in the active Blender scene. Designates the specified camera object as scene.camera. Validates that the target object exists and is of type CAMERA.

Input Schema

NameRequiredDescriptionDefault
nameNoAlias for camera_name.
task_idNoOptional task or workflow identifier for grouping related scene mutation operations.
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.
camera_nameNoName of the existing camera object to designate as the active scene camera.
target_nameNoAlias for camera_name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two useful traits: it mutates scene.camera and it validates that the target exists and is of type CAMERA. It is silent on failure behavior (error vs no-op), whether the previous active camera is restored on undo, and how the deprecated 'approved' flag interacts with the trusted approval mechanism referenced in the schema.

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

Conciseness5/5

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

Two short sentences, zero filler, with the action front-loaded and the validation detail following. Every sentence earns its place.

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 mutation tool with no annotations and no output schema, the definition covers purpose and validation but leaves out error semantics, approval requirements tied to the 'approved' parameter, and any return indication of success. Adequate to call correctly, but not complete for a scene-mutating operation.

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 schema already explains camera_name, the two aliases, task_id, and the deprecated approved flag. The description adds no extra meaning about alias precedence (anyOf allows exactly one of camera_name/name/target_name) or what task_id grouping implies, so it neither compensates nor detracts.

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 description names a specific verb and resource ('Switch the active scene camera', 'designates the specified camera object as scene.camera'), which is unambiguous. It implicitly separates itself from create_camera/configure_camera/edit_camera by being an activation operation rather than a creation or property edit, though no sibling is named explicitly.

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?

It says what the operation does but never states when to choose it over configure_camera, edit_camera, or create_camera, nor does it list prerequisites such as the camera already existing in the scene. The only guidance is the built-in validation, which is behavioral rather than selection guidance.

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