Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_material

Destructive

Assign a local material to selected SketchUp entities without recoloring unrelated users of an existing material, keeping edits isolated and predictable.

Instructions

Assign a local material without recoloring unrelated users of an existing material.

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": {
      "ids": "<ids>",
      "name": "<name>",
      "color_rgb_255": "<color_rgb_255>",
      "opacity": "<opacity>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
nameYes
opacityYes
operation_idYes
color_rgb_255Yes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine behavioral insight beyond that: the assignment is local, so existing shared material users are not recolored. However, it says nothing about the concurrency semantics implied by expected_revision or the role of operation_id, which matter for a destructive write.

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?

A single tight sentence with the key behavioral qualifier front-loaded. Nothing is wasted, though the brevity is more a function of omission than of disciplined editing.

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 destructive, six-required-parameter mutation with revision-based concurrency, one sentence is far from sufficient. The output schema relieves it of explaining return values, but the input contract and failure/conflict behavior remain undocumented.

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

Parameters2/5

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

All six parameters are required and schema description coverage is 0%, so the description must carry parameter meaning. It only obliquely implies a material name and color; ids, opacity, expected_revision, and operation_id receive no explanation anywhere.

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

Purpose3/5

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

The description names a specific verb and resource ('Assign a local material') and adds a meaningful qualifier about not recoloring unrelated users, but it never says what is being assigned to (entity ids) and does not differentiate itself from siblings such as sketchup_create or sketchup_combine.

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 when-to-use or when-not-to-use guidance and no alternative tool is named. The only usage signal is the implicit one in 'local material' versus an existing material, which the agent must infer.

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