Skip to main content
Glama

save_blend_file

Persist the current Blender scene to a .blend file, optionally choosing the path and whether to overwrite, so completed model edits are written to disk.

Instructions

Save the current .blend file.

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
pathNo
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about disk writes, what happens when 'overwrite' is false, whether unsaved/untitled files error out, or whether the operation can fail destructively. For a mutation tool with zero annotation coverage this is a significant gap.

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

Conciseness3/5

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

It is a single clean sentence with no filler, so nothing needs trimming. The terseness is under-specification rather than padding, which caps this dimension below 4.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but for a write-to-disk tool with two undocumented parameters and no annotations the definition is well short of complete. It omits error conditions, overwrite semantics, and how 'path' interacts with the "current file" framing.

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 0% for both parameters, so the description must compensate and mostly does not. The phrase "current .blend file" loosely implies that 'path' defaults to the existing file location, but 'overwrite' (default true) is never mentioned or explained, leaving the riskiest parameter undocumented anywhere.

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

Purpose3/5

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

The description gives a specific verb and resource ("Save the current .blend file"), which is better than a tautology. However, it does not distinguish this from the sibling save_as, and the presence of a 'path' parameter muddies the claim that only the "current" file is saved. An agent cannot tell from this text when the current-file save differs from save-as.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of the obvious alternative, save_as. The agent must infer that save_as is the choice when a new location is wanted and this tool is for persisting in place.

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