Opens a Blender file in background mode and returns its stored path data, enabling asset or scene workflows to extract file references without launching the full interface.
Return path info by opening blend_file in background Blender.
| Name | Required | Description | Default |
|---|---|---|---|
| blend_file | Yes |
| 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 declare readOnlyHint=true, and the description adds the behavior of opening a file in background Blender. This is useful extra context beyond the annotation. However, it does not disclose potential side effects like temporary file creation, performance impact, or whether the background Blender instance is persistent.
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 sentence with no filler. It is front-loaded with the action and clearly states the method (opening in background Blender). Every word contributes to understanding the tool's purpose.
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 one parameter and read-only annotation, and an output schema exists. The description covers the core operation. However, it does not mention any caveats, prerequisites, or how it differs from the non-CLI sibling, which is relevant context for an agent selecting among similar tools.
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 schema has no description for blend_file (coverage 0%), so the description must clarify the parameter. It does so by indicating that *blend_file* is the file to open, which adds meaning beyond the title 'Blend File'. However, it provides no additional details such as expected file extension, path requirements, or format constraints.
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 path info by opening a blend file in background Blender. The verb 'Return' and resource 'path info' are specific. However, it does not explicitly differentiate from the sibling tool get_blendfile_summary_path_info (without _for_cli), relying on the name suffix for distinction.
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?
There is no guidance on when to use this tool versus the non-CLI sibling or other summary tools. The description explains what it does but not the context or conditions that would make it the preferred choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.