Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_material

Assigns an exact material name to the active SOLIDWORKS part and returns the resulting density and mass, so you can verify model properties after a material change.

Instructions

Assign a material to the active part by its exact name from list_materials (e.g. '6061 Alloy', 'AISI 304', 'ABS'). Returns the resulting density and mass.

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": {
      "name": "<name>"
    },
    "name": "set_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesMaterial name exactly as listed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the mutation target ('active part') and the observable outcome ('returns the resulting density and mass'), but says nothing about permission requirements, whether an existing material is overwritten, or failure behavior for an invalid name.

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?

Two sentences, no filler. The action and target come first, the value-source constraint second, and the return values last — a well front-loaded structure.

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?

With no output schema, the description correctly compensates by naming the returned values (density and mass). For a single-parameter mutation tool this is nearly complete; only error/overwrite behavior for an unmatched or already-assigned material is left unstated.

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, and the description adds real meaning on top: it identifies list_materials as the authoritative source of legal values and stresses exact matching, which the schema alone does not convey. The examples further reduce ambiguity about string format.

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?

States a specific verb (assign) and resource (material), names the target object ('the active part'), and points to the sibling that supplies valid values (list_materials). An agent can distinguish this from set_color or set_custom_properties without opening any schema.

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 prerequisite workflow is explicit: names must come from list_materials and match exactly, with three concrete examples. What is missing is when-not-to-use guidance or what happens if the name is not found, but the positive usage path is unambiguous.

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