Skip to main content
Glama
sketchup-mcp2

sketchup-mcp2

by zinin

set_material

Assign or paint a material color on a SketchUp group, component instance, face, or edge using an existing material name, named color, or hex string.

Instructions

Assign a material (color) to a group, component instance, face or edge.

material: a material already in the model, matched by name without regard to case, is used as is (so an existing "Red" is used for "red"). Otherwise a named color — red, green, blue, yellow, cyan, turquoise, magenta, purple, white, black, brown, wood, orange, gray, grey — or a 6-digit hex string like "#a05030" (#rrggbb), in any case, maps to one lower-case material, found or created. Anything else fails with -32602. Painting a group/component affects only this instance (it is made unique first); painting a raw face/edge id (obtainable via get_selection) colors the shared definition — all instances show it.

Returns: JSON {id, name, type, bbox_mm{min,max}|null}. For a face or edge, type is "face" or "edge" and name is null.

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

Input Schema

NameRequiredDescriptionDefault
idYesEntity ID from a previous response (integer or its string form)
materialYesName of a material already in the model, named color, or 6-digit hex string like #a05030

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / properties / material / description
      Previous value: -"Named color or 6-digit hex string like #a05030"New value: +"Name of a material already in the model, named color, or 6-digit hex string like #a05030"
  2. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • addedInput schema / properties / id / description
      Added value: +"Entity ID from a previous response (integer or its string form)"
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • removedInput schema / properties / id / type
      Removed value: -"string"
    • addedInput schema / properties / material / description
      Added value: +"Named color or 6-digit hex string like #a05030"
  3. First observedv0.0.1

TDQS

A4.6/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 case-insensitive matching, accepted color names and hex syntax, the -32602 failure mode, instance-unique side effects for groups/components, shared-definition coloring for raw face/edge IDs, and the return shape.

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 first sentence is front-loaded and establishes purpose immediately. The remaining details are dense but mostly necessary for correct invocation, though the description runs several paragraphs and the color enumeration is lengthy.

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 mutation tool with no annotations, the description covers validation rules, side effects, uniqueness behavior, and return values. An output schema exists, but the description still supplies essential operational context an agent needs before calling it.

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 baseline 3 applies, but the description adds meaningful semantics beyond the schema: material matching rules, an exhaustive named-color list, hex format, failure behavior, and id provenance via get_selection.

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 and resource: assigning a material/color to a group, component instance, face, or edge. The target taxonomy is explicit enough that an agent can distinguish this from siblings such as transform_component or get_selection.

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?

Makes clear this is the tool for painting entities with a material and points to get_selection as the source for raw face/edge IDs. It lacks explicit when-not guidance, but no other sibling appears to perform material assignment, so the context is clear without exclusions.

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