Skip to main content
Glama
Sign In
blender-mcp

blender-mcp

by kleer001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_viewport_camera

Idempotent

Set the active camera for the Blender viewport by passing a camera object name, or use None to revert to the default camera.

Instructions

Set the active camera for the viewport. Pass camera object name, or None for default.

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

Input Schema

NameRequiredDescriptionDefault
cameraNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotation idempotentHint=true already indicates safe repeatability; description adds the behavioral detail that None resets to the default camera. No contradiction. It doesn't cover error behavior for invalid camera names, but given the annotation coverage this is acceptable.

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

Conciseness5/5

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

A single concise sentence that front-loads the purpose and packs the essential input nuance. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-optional-param tool with an output schema and idempotence annotation, the description is nearly sufficient. The only gap is not distinguishing from the similarly named sibling set_active_camera, which could cause selection ambiguity.

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

Parameters4/5

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

Schema has 0% description coverage, so the description carries the full burden; it explains the only parameter as a camera object name and clarifies None means default. This adds genuine semantic value beyond the raw schema, though it doesn't specify exact string format/case sensitivity.

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

Purpose4/5

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

Description clearly states the action (set) and resource (active viewport camera), and explains the parameter semantics (camera name or None). However, since sibling tool 'set_active_camera' exists with overlapping wording, the description doesn't explicitly differentiate between viewport-active vs scene-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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for setting the viewport camera and mentions the None default, but gives no explicit guidance on when to prefer this over sibling tools like set_active_camera or camera_look_at. No exclusions or alternative recommendations are provided.

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