Get a quick overview of a Blender scene: data-block counts, active workspace, and render engine. Use it to assess file state or confirm project settings before editing.
Return a summary of the blend file: data-block counts, active workspace, and render engine.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, and the description's 'Return' is consistent. The description adds no extra behavioral context beyond the annotation, such as prerequisites or environment expectations. This is adequate given the annotation covers the safety profile.
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 a single, front-loaded sentence that directly states the output. No filler or redundant phrases; every word adds value. It is concise and immediately comprehensible.
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?
For a nullary tool with an output schema and read-only annotation, the description is largely complete. However, it does not address the notable sibling variant _for_cli, which leaves the non-CLI vs CLI usage implicit. A brief note on environment would improve completeness.
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 input schema has zero parameters, so the baseline is 4. The description adds no parameter-level details, but none are needed. The tool is a nullary call, so no semantic gaps exist.
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?
The description clearly states the tool returns a blend file summary with specific contents (data-block counts, active workspace, render engine). This distinguishes it from sibling summary tools like missing_files, linked_libraries, path_info, and usage_guess. The verb 'Return' and resource are explicit.
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?
No guidance is given on when to choose this tool over alternatives. The description does not mention that it targets non-CLI contexts or how it differs from get_blendfile_summary_datablocks_for_cli. With many similar sibling tools, the agent gets no explicit routing help.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.