Skip to main content
Glama

Set Property

set_property
Destructive

Assign a single named property to a FreeCAD object, converting list values to vectors for vector-type properties.

Instructions

Set a single property by name on an object. Coerces lists → Vector for Vector properties; other values pass through.

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": {
      "handle": "<handle>",
      "name": "<name>",
      "value": "<value>"
    },
    "name": "set_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYes
handleYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds genuinely new information with the list→Vector coercion rule. However, it never says that an existing property value is overwritten, what happens for unknown property names or type mismatches, or whether a transaction must be open. Useful but incomplete beyond the annotation baseline.

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?

Two tight sentences, front-loaded with the core action, zero filler. The line break inside the coercion sentence is a formatting artifact but doesn't harm readability.

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?

This is a destructive mutation with no output schema and 25% schema coverage; the description should disclose overwrite semantics, failure behavior, and transaction/workspace requirements. Only the coercion rule is covered, leaving an agent unable to predict side effects of the call.

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 only 25% — only 'workspace' is documented, while 'handle', 'name', and 'value' are bare titles. The description partially compensates by explaining value coercion for Vector properties, but says nothing about what a handle refers to, naming conventions, or accepted value types beyond the Vector case.

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 single property by name on an object'), which is more precise than the title alone. It doesn't contrast itself with any sibling (e.g., set_visibility, transform, or run_script-driven property changes), so an agent must infer that this is the generic property mutator.

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 indication of when to use this versus other mutation tools, no prerequisites (must the object be in an open document/workspace, inside a transaction?), and no exclusions. The only guidance present is a type-coercion note, which is behavioral rather than usage-selection.

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

Deploy Server

Other Tools