Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

save_blend_file

Saves the active Blender file to disk, defaulting to its current path, and blocks accidental overwrites unless explicitly allowed.

Instructions

Save the active Blender file to disk. If filepath is omitted, saves to the current file path. Protects against accidental overwriting unless overwrite=True.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_blend_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
compressNoWhether to compress the saved .blend file (default True).
filepathNoDestination .blend file path. If omitted, saves over the currently opened .blend file.
overwriteNoWhether to overwrite an existing file if destination path already exists on disk (default False).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it does disclose the most important behavioral traits: omission of filepath falls back to the current file path, and overwrite protection is on unless overwrite=True. It does not say what happens on a blocked overwrite (error vs. prompt) or whether the write is atomic/irreversible, which keeps it below 5.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core action and followed by the two conditionals that matter. Slight redundancy with schema-documented filepath/overwrite descriptions is the only waste.

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

Completeness4/5

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

For a 5-parameter mutation tool with no annotations and no output schema, the description covers the essential safety semantics an agent needs before calling it. Remaining gaps (failure mode on blocked overwrite, return value) are minor given full schema coverage.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description restates the filepath and overwrite semantics but adds no syntax, constraints, or format detail beyond what the schema already documents, and says nothing about compress or task_id.

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

Purpose4/5

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

States a specific verb and resource ('Save the active Blender file to disk'), which clearly separates it from sibling loaders like load_blend_file and open_blend_file. It stops short of explicitly naming a sibling or contrasting behavior, so 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it is for persisting the currently open file. There is no explicit when-to-use/when-not guidance, e.g. no advice to use a save-as variant or open/load tools instead before saving.

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