Skip to main content
Glama

camera_view

Retrieve camera framing metadata to verify visual composition and confirm how a Blender scene is framed before rendering.

Instructions

Return camera framing metadata for visual verification.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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. It implies a read, but says nothing about whether an active camera is required, what happens when the optional name is omitted, or what occurs if the name matches nothing.

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?

One short, front-loaded sentence with no filler, which is appropriate in size. It is under-specified rather than verbose, so the brevity is a minor positive rather than a flaw 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 spelled out, and only one optional param is involved. Still, the agent is left without the meaning of that parameter or any hint of how this differs from the several sibling camera-inspection and capture tools.

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?

The single optional parameter `name` has 0% schema description coverage and the description does not explain it at all — it is unclear whether it means a camera name, an object name, or a scene name. With low coverage the description was required to compensate and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return camera framing metadata" gives a verb and a resource, so the basic action is legible. However, "framing metadata" is not defined (lens/focal length? sensor? viewport bounds?), and nothing distinguishes this from sibling reads such as get_camera_info or capture_camera_view.

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?

The phrase "for visual verification" gestures at a use case but gives no when-to-use condition, no prerequisites, and no named alternative. An agent cannot tell whether to call this or capture_camera_view / get_camera_info to check framing.

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