Skip to main content
Glama

modify_camera

Adjust a named Blender camera's settings to control lens, framing, and view for scene setup or rendering.

Instructions

Modify camera 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>",
      "settings": "<settings>"
    },
    "name": "modify_camera"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
settingsYes

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 provided, so the description carries the full burden, yet it discloses nothing about whether the mutation is reversible, what happens to unmentioned settings, or what permission/state constraints apply. A single sentence of pure restatement leaves all behavioral traits undocumented.

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?

The single sentence is short but not front-loaded with any useful content; it is under-specification rather than conciseness. Nothing here earns its place beyond echoing the title.

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?

For a mutation tool with a nested free-form settings object and a crowded family of camera-specific siblings, the definition is far too thin. The output schema lifts the burden of explaining return values, but the input side and the sibling disambiguation are entirely missing.

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% for two required parameters, one of which is a free-form object with additionalProperties: true and no stated shape. The description offers no key names, value ranges, or examples to compensate, so the agent cannot know what to put in "settings."

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?

"Modify camera settings" is essentially a restatement of the name modify_camera, adding only the word "settings." It gives no indication of what aspect of the camera is modified, and cannot be distinguished from siblings like configure_camera_lens, configure_camera_depth_of_field, or set_active_camera.

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?

There is no guidance on when to use this tool versus the many sibling camera tools, and no exclusions or prerequisites. An agent has nothing to route on.

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