Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_color

Set the color of active SOLIDWORKS parts or assembly components using color names, hex, or RGB values with optional transparency. The tool reports the color read back for each target.

Instructions

Set the colour of the active part, or of components of the active assembly. On a part the colour is stored in the part, so every assembly using it shows it (save the part to keep it). On an assembly, give components (names, or paths into sub-assemblies such as 'Door-1/Slat-3'; a list does several at once): the colour is stored in the assembly and the part files stay unchanged. Colour as a name (red, green, blue, yellow, orange, purple, cyan, magenta, pink, brown, white, black, grey, light_grey, dark_grey, silver, gold), hex '#rrggbb', or rgb [r, g, b] with 0 to 255 each; transparency from 0 (solid) to 1 is optional. Reports the colour read back for each target.

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_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
rgbNoInstead of color: [r, g, b], each 0 to 255
colorNoColour name or hex value '#rrggbb'
componentNoIn an assembly: one component, instead of the list
componentsNoIn an assembly: the components to colour
transparencyNo0 = solid, 1 = invisible. Left as it is when not given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses persistence semantics (part colour is stored in the part and must be saved to keep it; assembly colour is stored in the assembly and leaves part files unchanged) and that transparency is left untouched when omitted. It also states the return behaviour — the colour read back for each target.

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?

The main action is front-loaded and the paragraph is dense with useful detail rather than filler. The long inline colour-name list is justified by utility but makes the prose heavier than ideal.

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

Completeness5/5

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

For a zero-required-parameter mutation tool with no annotations or output schema, the definition covers target scoping, value formats, persistence consequences, and the reported result. Nothing an agent needs to invoke it correctly appears missing.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds real meaning beyond it: it enumerates the valid colour names, gives a concrete sub-assembly path example ('Door-1/Slat-3'), and clarifies that component/components are the assembly-scoped alternative. That goes well past the bare schema strings.

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 opening sentence gives a specific verb (set) and resource (colour) and scopes it to the active part or the components of the active assembly. An agent can immediately distinguish it from the sibling get_color, which reads rather than writes colour.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly frames the two usage contexts and which parameters apply to each ('On a part...' vs 'On an assembly, give components...'), and notes that a list colours several at once. It stops short of naming when to prefer this over a sibling such as get_color for verification, so it's clear guidance without explicit alternatives.

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