Skip to main content
Glama
dwgx

Blender Copilot MCP Server

by dwgx

set_camera

Configure scene camera position, rotation, focal length, target, and depth of field for precise shots.

Instructions

Configure the scene camera. Location is [x,y,z]. Rotation in degrees [x,y,z]. focal_length in mm (35=normal, 85=portrait, 200=telephoto). target: object name to point at. depth_of_field: {"enabled": true, "aperture": 2.8, "focus_object": "name", "focus_distance": 5.0}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
locationNo
rotationNo
focal_lengthNo
depth_of_fieldNo
Behavior2/5

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

No annotations; description only lists parameters without disclosing side effects, overwriting behavior, or restrictions. It does not fully compensate for missing annotations.

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 concise and front-loaded, but could be better structured (e.g., bullet points). No unnecessary words.

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?

Covers all parameters with examples, but lacks information on return values, behavior when parameters are null, and edge cases. Adequate for basic usage.

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?

Description adds meaning to all 5 parameters beyond the schema (which has 0% coverage). Provides example values and context for location, rotation, focal length, target, and depth of field.

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 it configures the scene camera and lists parameters. It distinguishes itself from sibling tools like 'render_set_camera' by focusing on scene camera settings, though not 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?

No guidance on when to use this tool vs alternatives (e.g., 'render_set_camera'), no prerequisites or context provided.

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/dwgx/blender-copilot'

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