Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

setup_camera_dof

Set camera depth of field to focus on a specific object or at a given distance for realistic blur effects in Blender.

Instructions

Configure depth of field on a camera. Focus on an object or at a specific distance.

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

Input Schema

NameRequiredDescriptionDefault
fstopNo
cameraYes
focus_objectNo
focus_distanceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the burden of explaining side effects, but it only provides a high-level purpose. It does not disclose how focus mode is selected, what happens if both focus_object and focus_distance are provided, or any required enabling steps.

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 two concise sentences that front-load the main purpose and add the key focus modes. Every word earns its place with no redundancy.

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?

Given there are 4 parameters, no annotations, and no parameter descriptions, the description is too sparse. It lacks critical details about parameter interactions, default behaviors, and output expectations, making it incomplete for reliable tool invocation.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It implicitly maps 'Focus on an object' to focus_object and 'at a specific distance' to focus_distance, but it does not explain the camera or fstop parameters, their units, defaults, or interactions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Configure depth of field') on a specific resource ('camera') and clarifies two focus modes ('Focus on an object or at a specific distance'). This clearly distinguishes it from broader camera tools like set_camera_property by focusing on DOF.

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 is provided on when to use this tool versus alternatives such as set_camera_property or camera_look_at. It does not mention exclusions or prerequisites, leaving the agent to infer applicability from the name alone.

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