Skip to main content
Glama

create_camera

Add a camera to a Blender scene with configurable lens, location, rotation, and name, and optionally make it the active scene camera.

Instructions

Create a camera.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_camera"
  }
}

Input Schema

NameRequiredDescriptionDefault
lensNo
nameNo
locationNo
rotationNo
set_activeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/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 of behavioral disclosure, and it discloses nothing. It does not say whether the new camera becomes the scene's active camera (set_active defaults to true, which is a side effect on scene state), whether it is linked to a collection, or what permissions or preconditions apply.

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 technically concise with no filler, but this is under-specification rather than economy. Brevity here removes information an agent needs rather than trimming redundancy.

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 that is the only thing covered. For a 5-parameter creation tool with no annotations and zero parameter documentation, the description is far short of what an agent needs to call it correctly.

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 exist with 0% schema description coverage, and the description does not mention any of them. Critical ambiguity is left unaddressed: units and meaning of lens (default 50), the format/space of location and rotation arrays, and the consequence of set_active defaulting to true.

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?

"Create a camera" only restates the tool name and title; it adds no resource detail beyond the name. It gives no signal about how this differs from siblings such as modify_camera, get_camera_info, or create_object, which an agent must distinguish before choosing.

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 prerequisite context (e.g. whether a scene/collection must exist), and no mention of alternatives such as modify_camera for changing an existing camera. The only implied usage is the bare act of creation.

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