Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

set_property

Update a FreeCAD Data-tab property or bind an expression to a model value, with undo support for safe changes.

Instructions

Update a Data-tab property (Pad.Length, Fillet.Radius, VarSet fields) or bind an expression (undoable).

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": {
      "object_name": "<object_name>",
      "property_name": "<property_name>"
    },
    "name": "set_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoDimensions
valueNo
doc_nameNo
expressionNo
object_nameYes
property_nameYes
property_typeNo
clear_expressionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false and idempotent=false, so the safety profile is largely covered. The description adds one genuine behavioral fact not in the annotations: changes are 'undoable'. However, it omits critical behavior such as whether value and expression are mutually exclusive, whether set_property fails when the property does not exist, and why the operation is flagged non-idempotent.

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?

A single dense sentence with the action front-loaded and no filler; the examples and the 'undoable' caveat each earn their place. It is efficient but borders on terse given the parameter surface it must cover.

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?

An output schema exists, so return values need not be described, but for an 8-parameter mutation tool with 0% schema coverage the description is too thin: the semantics of half the parameters and the risk conditions for a write operation are left for the agent to guess.

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% across 8 parameters, so the description must carry the load. It only implicitly maps to property_name/value/expression via its examples; group, doc_name, property_type, and clear_expression are entirely unexplained, and the interaction between value, expression, and clear_expression is never clarified.

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+resource: 'Update a Data-tab property', with concrete examples (Pad.Length, Fillet.Radius, VarSet fields), plus a second mode 'bind an expression'. An agent can tell this mutates FreeCAD property values, though it does not explicitly distinguish itself from siblings like set_appearance or create_varset.

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?

Usage is implied by the two named modes (set a value vs. bind an expression), but there is no explicit when-to-use/when-not guidance, no prerequisites (must a document be open? must the object exist?), and no mention of alternatives for expression editing.

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