Blender-Mind-MCP

blender_setup_camera

Create and position a camera in Blender, set a look-at target for focus, and adjust focal length to frame scenes accurately.

Instructions

Creates and positions the scene camera with look-at target tracking and focal length lens adjustments.

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": "blender_setup_camera"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the camera
`look_at`	No	[x, y, z] focus target coordinate to aim at
`location`	No	[x, y, z] camera placement coordinates
`focal_length`	No	Focal length in mm (default: 50mm)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does say the camera is created and positioned, which implies scene mutation, but it doesn't mention whether an existing camera is replaced, a new camera is added, or what defaults apply when location is missing. For a tool that changes scene state, this is only minimal transparency.

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?

The description is a single, front-loaded sentence with no filler, repetition, or off-topic information. It communicates the operation and the primary camera adjustments efficiently and each phrase contributes meaning.

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?

This is a simple 4-parameter tool with an input schema that already documents all parameters, and no output schema is required. The description gives the core purpose, but the lack of annotations and the absence of details about side effects, defaults, or scene expectations makes it merely adequate rather than fully context-rich for an autonomous agent.

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?

The input schema covers 100% of the parameters, so the baseline is 3. The description adds conceptual value by mapping the schema parameters to camera behaviors via 'look-at target tracking' and 'focal length lens adjustments,' but it doesn't add concrete details beyond what the schema already provides.

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 uses a specific verb and resource: 'Creates and positions the scene camera' with look-at target tracking and focal length adjustments. This clearly conveys what the tool does and is sufficiently distinct from the sibling tools such as blender_setup_lighting, though it doesn't explicitly name alternative tools.

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?

The description doesn't state when to use this tool versus the alternatives, nor does it specify any workflow context, prerequisites, or exclusions. The intended use is inferable from the verb and camera naming, but there is no explicit guidance for an agent deciding between this and tools like blender_capture_viewport or blender_inspect_scene.

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

Deploy Server