Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

save_as

Save the active SolidWorks document to an explicit file path, including fresh documents with no filename. Returns saved path and success status.

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 use: scripted runs that build or update a document, save it to a user-controlled directory, and hand the resulting path to a downstream step.

Caveats:

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

  • Resolve special folders through Windows or an explicit user-provided path. Desktop and Documents locations may be redirected by OneDrive or organization policy; do not guess a hard-coded location.

Example — save a fresh part: save_as(r"C:\CAD\output\bracket_v1.SLDPRT")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
Behavior5/5

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

Despite no annotations, the description thoroughly discloses behavioral traits: it sets the filename, subsequent save_active_document will write to the same path, it describes the return dict, and it warns that passing wrong extension causes failure. It also mentions caveats about directory existence and special folders.

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?

The description is well-structured with sections (Spanish/English, args, returns, common use, caveats, example) and is front-loaded with the key distinction. It could be slightly more concise, but it is efficiently organized and every sentence adds value.

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?

Given the tool complexity and lack of output schema, the description is complete: it explains the return dict shape, error behavior, and caveats. It covers all necessary information for an agent to use the tool correctly.

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?

The only parameter 'path' has no schema description (0% coverage), but the description adds significant meaning: absolute file path including extension, lists valid extensions with their document types, and warns about wrong extension causing failure. This fully compensates for the lack of schema description.

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 it saves the active document to an explicit path (Save As), and explicitly differentiates it from the sibling save_active_document by noting that save_as works for fresh documents without a filename, while save_active_document only works for already-named docs. This is a specific verb and resource, distinguishing it from siblings.

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?

The description provides explicit guidance on when to use this tool (for fresh, never-saved documents) versus when to use the sibling (already saved documents). It also gives a common use case (scripted runs) and caveats (parent directory must exist, special folder handling). This is comprehensive.

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/solidworks-mcp'

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