Skip to main content
Glama

save_as

Saves the current Blender file to a specified new path, with optional overwrite, so you can create a copy or relocate your project.

Instructions

Save the blend file to a new path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "save_as"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 and does not meet it. It says nothing about what happens when the target path already exists, how the 'overwrite' flag changes that behavior, whether the current file becomes the new path, or what errors (permissions, missing directory) may occur for a file-writing operation.

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?

A single short sentence with the destination concept front-loaded and no filler. It is efficient, though the terseness is under-specification rather than disciplined brevity.

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?

This is a destructive-adjacent file mutation with no annotations, no parameter descriptions, and an undocumented overwrite flag; the output schema covers return values but not behavior. Given the complexity and risk of writing files, the definition leaves too much for an agent to guess.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it only echoes the 'path' parameter as 'a new path'. The 'overwrite' parameter — the one with genuinely ambiguous behavior (error vs. silent replace vs. auto-rename) — is never mentioned, leaving the second parameter undocumented everywhere.

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?

The description gives a specific verb and resource ('Save the blend file') plus a scope qualifier ('to a new path'), so an agent knows this is a write-to-new-location operation. It does not explicitly distinguish itself from the sibling 'save_blend_file', though the 'as' semantics imply the difference.

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?

'To a new path' weakly implies you should use this instead of an in-place save when a different destination is wanted, but the description never states when to prefer 'save_blend_file' or what conditions make this tool appropriate. The usage guidance is inferred rather than stated.

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