Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

get_color

Read the RGB color and transparency of the active SOLIDWORKS part or selected assembly components, and identify whether each color is set in the assembly or inherited from the part file.

Instructions

Read the colour (rgb 0 to 255) and transparency of the active part, or of components of the active assembly (all parts when none are named). For a component it also says whether the colour is set in the assembly or comes from the part file. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
componentNoIn an assembly: one component, instead of the list
componentsNoIn an assembly: the components to read (default: every part)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 burden and does real work: it declares read-only behavior, defines the default scope when no components are given, and discloses a non-obvious return nuance (whether colour is set in the assembly or inherited from the part file). It does not mention failure modes such as no active document.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the core action front-loaded, the scope qualifier immediately after, and the special-case note last. No filler wording and no repetition.

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?

Given no annotations and no output schema, the description handily covers what the tool returns (rgb 0-255, transparency, assembly-vs-part origin) and how scope defaults. Only edge-case behavior — no active document, invalid component name — is left uncovered.

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 coverage is 100% and both properties already document 'one component, instead of the list' and 'default: every part', so the description largely restates schema content. The rgb 0-255 range it adds describes the return value rather than parameter meaning, leaving little net semantic gain on inputs.

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 and resource ('Read the colour ... and transparency'), states the object scope ('active part, or components of the active assembly'), and adds 'Read-only,' which cleanly separates it from the mutation sibling set_color 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 Guidelines4/5

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

It makes the usage context explicit — reads apply to the active part or to assembly components, and 'all parts when none are named' defines the default call shape. It stops short of naming set_color as the write-side counterpart, so routing guidance is clear but not fully spelled out.

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