Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

save_document

Saves the current FreeCAD document to disk, optionally to a new .FCStd path, so edits can be captured or a copy created at a specified location.

Instructions

Save the document to disk, optionally to a new .FCStd path.

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_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says the document is saved to disk and may use a new .FCStd path, but it does not disclose overwrite behavior, whether an open document is required, whether saving to a new path changes the active document, or what side effects or errors may occur.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no redundant wording. It communicates the core action and optional path behavior efficiently.

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?

For a mutation tool with no annotations, no output schema, and 0% schema description coverage, the definition is too sparse. It leaves important invocation details unclear, including document identification, save-target behavior, and whether overwriting is possible.

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 explain the two parameters. It adds that 'path' is optional and refers to a new .FCStd target, but it does not define the expected path format, extension handling, or what the 'document' parameter identifies.

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 states a specific verb and resource: save the document to disk, optionally to a new .FCStd path. It is clear what the tool does, but it does not differentiate from sibling tools such as export_document or explain whether the document must already be open.

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?

Usage is only implied by the tool name and description. There is no explicit guidance on when to use this instead of export_document, close_document, or open_document, and no prerequisites or exclusions are stated.

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