Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

close_document

Close a specific CAD document in the headless FreeCAD worker, or the active document when no document is provided.

Instructions

Close a document; without an argument the active document is closed.

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": "close_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden of behavioral disclosure and does not meet it. It does not say whether unsaved changes are discarded or saved, whether the call errors on an unknown/already-closed document, or whether it is reversible. For a state-changing lifecycle operation this is a meaningful gap.

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?

One short sentence with the default behavior front-loaded after the primary action; nothing is redundant. It is close to optimally sized for the amount of information it chooses to convey, though the semicolon construction is slightly terse.

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

Completeness3/5

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

The tool is simple (one optional parameter, no output schema, no nested objects), so the description is proportionally adequate. It is still missing the two things an agent would most want: the accepted identifier format and the fate of unsaved changes on close.

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%, so the description must compensate. It does add real meaning by establishing that the single parameter is optional and what omission does, but it never says what form the identifier takes (name, path, or handle), leaving the parameter's value space unexplained.

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 ("Close a document") and adds the default-scope behavior when no argument is given. It is clearly distinguishable from siblings like open_document and save_document by the verb alone, though it never names them.

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?

It tells the agent how to invoke it in both modes (explicit document vs. no argument = active document), which implies the usage context. It gives no when-to-use guidance relative to alternatives and no preconditions, such as whether the document must be open or whether saving first is required.

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