Retrieve complete Blender scene data including objects, hierarchy, frame range, and render settings for quick analysis.
Get comprehensive scene information: objects, hierarchy, frame range, render settings.
Returns scene name, active object, object count with type breakdown, full object list with transforms, collection hierarchy, and render config.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. 'Get' and 'Returns' strongly imply a read-only operation with no scene mutation, and the description lists the returned data. However, it does not explicitly state that the tool has no side effects or that it only reads current scene state.
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?
The description is compact and front-loaded with the core purpose, followed by a concise enumeration of return contents. Every sentence adds useful information and there is no filler or repetition that detracts from clarity.
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?
The tool is simple with no parameters and no output schema, so the description must explain what is returned, which it does well by listing scene name, active object, object data, hierarchy, and render settings. It could be more complete with a note about the structure or units of transforms, but the listed return areas are sufficient for an agent to understand the tool's scope.
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 has zero parameters and the schema description coverage is 100%, so there are no parameter semantics to clarify. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on return content rather than inputs.
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 and resource: 'Get comprehensive scene information' with a clear list of categories (objects, hierarchy, frame range, render settings). It is clear what the tool does, though it does not explicitly differentiate itself from similarly-named sibling tools like get_scene_summary or get_scene_for_model.
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?
The description gives no guidance on when to use this tool versus alternatives. It does not mention get_scene_summary, list_objects, or get_object_info, nor does it say when the more comprehensive output would be preferable to a lighter-weight option.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.