Skip to main content
Glama

configure_camera_depth_of_field

Adjust a Blender camera's depth of field by setting enabled state, f-stop, focus object, or focus distance to control blur and focus.

Instructions

Configure camera depth of field.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
fstopNo
enabledNo
focus_objectNo
focus_distanceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden and discloses nothing: not whether this mutates render settings, whether changes apply to the named camera only, what happens when enabled is toggled, or whether focus_object overrides focus_distance.

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

Conciseness2/5

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

A single short sentence is technically efficient, but here brevity reflects under-specification rather than discipline; there is no front-loaded detail worth reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, but for a 5-parameter mutation tool with no annotations and no parameter documentation, the definition leaves nearly everything an agent needs unstated.

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

Parameters1/5

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

Five parameters with 0% schema description coverage and only bare titles. The description says nothing about fstop, focus_object, focus_distance, enabled, or the required name, so nothing compensates for the total absence of schema documentation.

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

Purpose2/5

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

"Configure camera depth of field" restates the tool name verbatim and adds no scope, target, or effect detail. It does not distinguish this from siblings like configure_camera_lens or focus_camera_on_object.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, no mention of alternatives such as configure_camera_lens or focus_camera_on_object. The agent has no basis for choosing among the camera configuration tools.

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