Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

set_parameter

Set a model parameter by reference and rebuild the model automatically. Accepts numbers or FreeCAD expressions like 40 mm or Box.Length * 2 to update geometry.

Instructions

Set a parameter and rebuild the model.

reference is either Object.Property (for example Box.Length) or a spreadsheet alias. value is a number or a FreeCAD expression such as 40 mm or Box.Length * 2.

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": {
      "reference": "<reference>",
      "value": "<value>"
    },
    "name": "set_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
documentNo
referenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool rebuilds the model, which is the key non-obvious side effect, but omits permission requirements, what happens on an invalid reference or unit mismatch, whether the rebuild can fail or is expensive, and whether the change is persisted to disk.

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?

Front-loaded with the action and its side effect, followed by tight per-parameter format notes. No filler sentences; the only gap is structural, not verbosity.

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

Completeness4/5

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

For a three-parameter mutation tool with no annotations and no output schema, the description covers the core action, the side effect, and the two required parameter formats with examples. The unaddressed ``document`` parameter and absent failure/return behavior are the remaining holes.

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 well for two of three parameters, giving the ``Object.Property`` / spreadsheet-alias grammar for reference and the number-or-expression form with concrete examples for value. The optional ``document`` parameter is never mentioned in either schema or description, leaving the agent to guess whether it defaults to the active document.

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?

States a specific verb and resource ("Set a parameter") plus the consequential side effect ("rebuild the model"). An agent can distinguish this from read-only siblings like parameters or inspect_document, though it never explicitly names a sibling.

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?

No explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as recompute (which presumably rebuilds without changing a value) or parameters (which presumably reads them). The context is implied by the verb, but nothing tells the agent which tool to pick when it only needs a rebuild.

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