Skip to main content
Glama

save_as

Save the active CAD document to a specified file path, even for newly created documents without a filename. Sets the document's path for subsequent saves.

Instructions

Guardar el documento activo a una ruta explícita (Save As).

A diferencia de save_active_document, esta sí funciona con piezas recién creadas que aún no tienen nombre de archivo. Una vez guardadas, los siguientes save_active_document escriben a la misma ruta. [en: Save the active document to an explicit file path. Unlike save_active_document — which only works on docs that already have a filename — save_as handles a fresh, never-saved document and sets its filename in one call. Subsequent save_active_document calls then save back to this same path.]

Args: path: Absolute file path INCLUDING extension. SolidWorks infers the document type from the extension: .SLDPRT parts .SLDASM assemblies .SLDDRW drawings Passing the wrong extension for the active doc type causes SaveAs to fail.

Returns the same dict as save_active_document:

  • name: document title

  • path: filesystem path written to

  • saved: True if save succeeded

  • errors / warnings: 0 (the simpler SaveAs variant doesn't expose these — use save_active_document on a subsequent save if you need the bitmasks).

Common autoparts use: scripted runs that build a part from scratch, save it to a customer-controlled directory, and hand off the path to a downstream step.

Caveats:

  • The parent directory must exist; save_as does NOT mkdir.

  • En Windows en español con OneDrive (la configuración típica del cliente PYME), el escritorio del usuario es C:\Users\<user>\OneDrive\Escritorio, NO C:\Users\<user>\Desktop (esa ruta no existe). Si el usuario dice "guárdalo en el escritorio" sin path explícito, prueba primero la ruta de OneDrive\Escritorio. [en: On Spanish-Windows + OneDrive — the typical PYME setup — the user's Desktop is C:\Users\<user>\OneDrive\Escritorio, not C:\Users\<user>\Desktop (which doesn't exist). When the user says "save it to the Desktop" without an explicit path, try the OneDrive\Escritorio path first.]

Example — save a fresh part: save_as(r"C:\Users\danie\OneDrive\Escritorio\bracket_v1.SLDPRT")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses: behavior for fresh vs. already-saved documents, sets filename for future saves, does not create directories, failure cases (wrong extension), and region-specific desktop path handling. Also describes return dict differences.

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?

Description is well-structured with bilingual sections, bullet points for args/returns/caveats/example. Some repetition between Spanish and English but acceptable for clarity. Not overly verbose given the content.

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?

No output schema, but description specifies return dict and its keys. Parameter is fully explained. Given the tool's simplicity (1 param, no enums), the description covers all necessary behavioral and contextual information.

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?

Single 'path' parameter is described in detail: must include extension, SolidWorks infers document type from extension, lists valid extensions and their types, and warns that wrong extension causes failure. Schema coverage is 0%, but description fully compensates.

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 that save_as saves the active document to an explicit path, contrasting with save_active_document which only works on already-named documents. It explicitly handles fresh, unsaved documents and sets the filename.

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

Usage Guidelines5/5

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

Explicitly compares with save_active_document, stating when to use save_as (for fresh documents) and when to use save_active_document (for subsequent saves). Also includes caveats about directory existence and OneDrive path for Spanish Windows.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/MCP_CAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server