Skip to main content
Glama

blender_camera

Create and control cameras in Blender scenes. Adjust lens, sensor, position, and rotation to set up views.

Instructions

Create and control cameras in Blender scenes.

Supports multiple operations through the operation parameter:

  • create_camera: Create a new camera

  • set_active_camera: Set the active camera

  • set_camera_lens: Adjust camera lens and sensor settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoCamera operation typecreate_camera
camera_nameNoName for the cameraCamera
locationNoCamera position coordinates
rotationNoCamera rotation angles in degrees
target_locationNoTarget position for look_at operations
lensNoCamera lens focal length in mm
sensor_widthNoCamera sensor width in mm
fovNoField of view in degrees
clip_startNoNear clipping distance
clip_endNoFar clipping distance

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so behavioral burden falls on description. It lists operations but doesn't disclose side effects, permissions, or safety considerations. Basic transparency but not comprehensive.

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?

Description is short and uses bullet points for operations, making it scannable. It could be slightly more structured with explicit sections, but overall efficient.

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?

With 10 parameters and an output schema, the description is minimal. It doesn't cover prerequisites like needing an active scene or naming constraints, but is adequate for basic use.

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 description adds no extra meaning beyond the schema. It mentions operation types and lens settings, but these are already described in the parameters.

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?

Description clearly states the tool creates and controls cameras in Blender, with specific operations listed. However, it doesn't differentiate from sibling tools that might also involve camera management, such as blender_scene.

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?

No guidance on when to use this tool versus alternatives, nor any preconditions or exclusions. The description only explains what the tool does, not when it's appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server