Retrieve high-level Blender scene configuration—active camera, render engine, FPS, frame range, unit system, and object counts—to inspect scene state before making changes.
Retrieves high-level scene configuration: active camera, render engine (Cycles / EEVEE), FPS, frame range, unit system, and object counts by type.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. 'Retrieves' clearly signals a non-mutating read, and it lists the exact categories of data returned, but it says nothing about side effects, permissions, or cost/latency characteristics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence that names the operation immediately and then enumerates the returned fields. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so the description needn't detail return structure, and it still gives a useful preview of what is returned. For a zero-parameter read tool this is essentially complete; only the read-only/side-effect guarantee is left implicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4. No parameter meaning can be added beyond the empty schema, and the description correctly does not pretend otherwise.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Retrieves) and resource (scene configuration) and enumerates exactly what is returned: active camera, render engine, FPS, frame range, unit system, object counts. This is enough to distinguish it from siblings like blender_inspect_object or blender_get_outliner, though it does not explicitly name those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than stated: an agent can infer this is a scene-wide orientation call. There is no explicit guidance on when to prefer it over blender_inspect_object or blender_get_outliner, nor any stated prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.