Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_custom_properties

Set or delete custom properties on the active SOLIDWORKS part, assembly, or drawing—file-level by default or for a named configuration—and read back typed and resolved values.

Instructions

Set or delete custom properties of the active document (part, assembly or drawing): properties gives name -> text (a number is written as its text; the result says so), delete lists names to remove. They go on the file itself unless configuration names one of its configurations. A value can link to another property, e.g. '"SW-Mass@Bracket.SLDPRT"'. Every property touched is read back: value as typed and resolved value. Nothing changes if any input is refused.

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

Input Schema

NameRequiredDescriptionDefault
deleteNoNames of properties to remove
propertiesNoName -> value to set, e.g. {"PartNo": "BR-104", "Description": "Bracket"}
configurationNoA configuration of the part or assembly (default: the file's own properties)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied the description carries the full behavioral burden and does so well: it discloses number-to-text coercion, property-link syntax with a concrete example, that every touched property is read back with both typed and resolved values, and the atomic guarantee that nothing changes if any input is refused. Missing only permission/precondition context and whether an empty value clears a property.

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?

Four tight sentences, each front-loading a distinct fact (scope, parameter roles, storage target, return behavior), with the atomicity guarantee as a strong closer. Slightly dense parenthesis-heavy phrasing but no filler.

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 3-parameter mutation tool with no annotations and no output schema, the description covers targeting, coercion rules, return values, and failure atomicity — nearly everything an agent needs. It stops short of describing error reporting or the interaction of delete with a configuration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: values must be text (numbers are stringified), the configuration parameter's file-vs-configuration targeting is spelled out, and a link expression format is demonstrated. That is genuine added semantics rather than repetition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb pair and resource ('Set or delete custom properties') and immediately bounds the target ('of the active document (part, assembly or drawing)'), which distinguishes it from the read-only sibling list_custom_properties without naming it.

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 explains which parameter serves which intent (properties to set, delete to remove) and where the write lands (the file itself unless configuration names one), which is useful routing context. However, it never states when to prefer this tool over alternatives or any when-not conditions, so guidance remains implicit.

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