Skip to main content
Glama

configure_camera_lens

Adjust a Blender camera's lens, projection type, and orthographic scale to control framing and perspective for renders and animations.

Instructions

Configure camera lens settings.

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_lens"
  }
}

Input Schema

NameRequiredDescriptionDefault
lensNo
nameYes
typeNo
ortho_scaleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire burden of behavioral disclosure, and it says nothing beyond implying mutation. It omits whether the change targets the active camera or the named one, what happens to unspecified optional fields, whether it affects orthographic vs perspective behavior, and whether it requires a specific mode or permissions.

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

Conciseness3/5

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

It is a single short, front-loaded sentence with no padding, so nothing is wasteful. The problem is the opposite of verbosity: the sentence is too thin to carry the information load, so brevity is not earning its place here.

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?

An output schema exists, so return values need not be explained, but everything else is missing: the tool mutates camera state with no annotations, no documented parameters, and no guidance on required setup. For a four-parameter mutation tool, this is substantially under-described.

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?

Schema description coverage is 0% across four parameters, and the description compensates for none of them. Critical ambiguities go unaddressed: `lens` (millimeters?), `type` (what string values are valid, and why no enum is declared), and `ortho_scale` (only meaningful for orthographic cameras, which the agent cannot know from either field).

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?

The description restates the tool name almost verbatim: "Configure camera lens settings" for configure_camera_lens. It never identifies which lens properties are affected (the schema's `lens`, `type`, `ortho_scale` are invisible here) or how it differs from siblings like `modify_camera` or `configure_camera_depth_of_field`, leaving the agent unable to distinguish it from other camera-configuration 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?

There is no when-to-use guidance, no stated preconditions (e.g. an active camera must exist, or `name` must reference an existing camera), and no mention of alternatives. The agent must guess whether this is the right tool versus `modify_camera`, `create_camera`, or `configure_camera_depth_of_field`.

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