Skip to main content
Glama
SketchUp MCP

SketchUp MCP

by camilin7483

set_material

Assign a material or color to a SketchUp component by its ID or name, enabling targeted scene material updates through the MCP server.

Instructions

Aplica material/color a componente. Colores: Red, Blue, #ff0000, etc.

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

Input Schema

NameRequiredDescriptionDefault
colorNo
materialNoRed
id_or_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 for a mutation tool. It does not say whether existing materials are overwritten, how 'material' and 'color' interact when both are given (material defaults to 'Red' while color defaults to an empty string), or what happens when the target cannot be resolved. The output schema covers return values, but the side effects of the write are undisclosed.

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?

Two short sentences with the operation front-loaded and the value format immediately after; nothing is padded. The tradeoff is that terseness borders on under-specification rather than efficient precision.

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

Completeness2/5

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

For a three-parameter mutation tool with no annotations and zero schema description coverage, the description is too thin. It omits how the component is identified, how material and color precedence works, and what a failed lookup does; only the color format hint exceeds what the structured fields already say.

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 description coverage is 0%, so the description must compensate, and it partially does: 'Red, Blue, #ff0000, etc.' clarifies that colors are supplied as names or hex codes, which the bare 'string' schema does not convey. It says nothing about the required id_or_name parameter (ID vs name resolution) or about what values 'material' accepts, leaving the two most consequential parameters undocumented.

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

Purpose4/5

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

The description states a specific verb and resource ('Aplica material/color a componente'), so an agent can tell it changes a component's appearance rather than creating or transforming it. It does not name any sibling (create_component, transform_component) to sharpen the boundary, but the operation itself is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, and no prerequisites such as whether the component must exist, be selected, or be in the active scene. The only usage-adjacent content is the color format examples, which is not a when-to-use rule.

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