Skip to main content
Glama

get_camera_info

Retrieves camera details from Blender scenes to inspect settings and verify camera configuration for rendering or animation.

Instructions

Get camera information.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 full disclosure burden, yet it only implies a passive read via the verb 'Get'. It says nothing about whether an error is returned for unknown names, whether all cameras are returned when name is omitted, or what the output schema contains. This is a substantial gap for a tool with zero annotation coverage.

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?

One short front-loaded sentence with no filler, but the brevity reflects under-specification rather than discipline. There is no structure because there is almost no content.

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 the input side and the selection semantics remain unaddressed. For a tool with an optional lookup parameter and no annotations, the description should state what happens with and without 'name'.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter 'name' is undocumented, yet the description never mentions it. An agent cannot tell from either source whether 'name' is a lookup key, a filter, or an optional label, nor what the default null behavior means.

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 is essentially a restatement of the tool name: 'Get camera information' adds no verb specificity beyond what 'get_camera_info' already conveys. It does not say whether it returns one camera or all cameras, nor what 'information' comprises (lens, transform, DOF), which matters given siblings like camera_view and get_active_object.

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 guidance on when to use this rather than get_active_object, camera_view, or get_scene_summary. The only hint of scope is the optional 'name' parameter, which the description never references, so the agent must infer the selection semantics itself.

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