Save the current Blender scene to its existing file, or save a copy to a specified filepath for versioning or relocation.
Save the current scene. If filepath is provided, save-as to that path.
| Name | Required | Description | Default |
|---|---|---|---|
| filepath | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0+hardened.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry full behavioral disclosure. It only says 'save', omitting details about overwriting, permissions, side effects, or what happens when filepath is null. This is a significant gap for a mutation tool.
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, concise sentence that front-loads the core action and efficiently covers the optional parameter. No wasted words.
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 optional parameter, so the description is close to sufficient. However, it lacks behavioral context like overwrite semantics and return behavior, which an agent might need for correct invocation, especially without annotations.
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 0% description coverage, so the description must compensate. It explains that filepath triggers 'save-as' behavior, clarifying the parameter's conditional role beyond the bare schema type. This adds meaningful value.
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 a specific action ('save') on a specific resource ('current scene'), and the optional filepath behavior distinguishes it from siblings like load_file and export_file. The purpose is unambiguous and immediately actionable.
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 implies usage for saving the scene, but it does not explicitly mention when to prefer save_file over export_file or other related tools. No exclusions or alternative guidance is provided, leaving the agent to infer the right context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.