Skip to main content
Glama
naab007

BlenderMCP

by naab007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

close_blender

Close Blender instances gracefully or force quit, optionally saving the current .blend file before exiting to prevent data loss.

Instructions

Close Blender. Works for an instance started with start_blender() and, via the addon socket, for one the user launched by hand.

Parameters:

  • force: If True, kills the managed process immediately instead of asking Blender to quit gracefully via its Python API (default False).

  • save: If True, save the current .blend (if it has a path) before quitting. Unsaved changes are otherwise discarded without a prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNo
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / save
      Added value: +{
+  "default": false,
+  "title": "Save",
+  "type": "boolean"
+}
  2. First observedv1.5.5

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description explains the behavior of both parameters: force (kill vs graceful quit) and save (save changes vs discard without prompt). This gives clear expectations of side effects, especially regarding unsaved changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, using only a few sentences to convey purpose, scope, and parameter behavior. No redundant or extraneous information is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with no output schema, the description provides sufficient context: it explains what it does, when it works, and the effects of each parameter. No additional information is needed for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (force and save) are fully described in the description, matching the schema. The explanations clarify their boolean meanings and consequences, covering all parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: closing Blender. It also specifies the types of instances it operates on (those started with start_blender() and user-launched via the addon socket), leaving no ambiguity about its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when the tool is applicable by distinguishing between managed and user-launched instances. It does not explicitly compare to alternatives, but the scope clarification effectively guides usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools