Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_camera_property

Adjust Blender camera settings by setting properties like lens, clipping, depth of field, sensor, ortho scale, shift, or type. Provide camera name, property, and value to update it.

Instructions

Set a property on a camera.

Args: object_name: Name of the camera object. property: Property to set. One of: lens, clip_start, clip_end, sensor_width, sensor_height, dof.use_dof, dof.focus_distance, dof.aperture_fstop, ortho_scale, shift_x, shift_y, type, sensor_fit. value: The value to set.

Returns: Confirmation dict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
propertyYes
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • addedInput schema / properties / object_name
      Added value: +{
+  "title": "Object Name",
+  "type": "string"
+}
    • addedInput schema / properties / property / enum
      Added value: +[
+  "clip_end",
+  "clip_start",
+  "dof.aperture_fstop",
+  "dof.focus_distance",
+  "dof.use_dof",
+  "lens",
+  "ortho_scale",
+  "sensor_fit",
+  "sensor_height",
+  "sensor_width",
+  "shift_x",
+  "shift_y",
+  "type"
+]
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "property",
-  "value"
-]New value: +[
+  "object_name",
+  "property",
+  "value"
+]
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It implies a mutation and mentions a confirmation dict, but does not disclose side effects, permission requirements, reversibility, or failure modes for an invalid property/value combination.

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?

The description is appropriately front-loaded with its purpose, followed by concise Args and Returns sections. The property enumeration duplicates the schema enum, but the overall structure is efficient and readable.

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?

For a mutation tool with no annotations and 0% schema description coverage, the description leaves important gaps: value typing, when to use this tool, and behavioral side effects are missing. The output schema covers the return value, but the input and usage context remain underspecified.

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 description coverage is 0%, so the description must compensate. It names all three parameters and lists the valid property values, but 'value' is only described as 'The value to set' with no indication of expected type or range per property, so the explanation remains incomplete.

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 states a specific verb and resource: 'Set a property on a camera.' It is clear what the tool does, but it does not distinguish itself from the many sibling set_*_property tools beyond naming the camera object type.

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 given about when to use this tool versus alternatives such as set_object_property or other camera-related tools. The description only states the mechanics of the operation, leaving use context implicit.

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