Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_group

Group root-level sibling instances into a named group while preserving their geometry and materials, avoiding boolean rebuilding. Use it to organize related model parts without altering existing geometry.

Instructions

Group explicit root-level sibling instances without boolean rebuilding their geometry/materials.

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>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
nameYes
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already cover mutability and safety (readOnly=false, destructive=false, idempotent=false). The description does add one real behavioral fact beyond them: geometry and materials are preserved rather than boolean-rebuilt. It says nothing about revision/concurrency requirements, whether grouping can fail, or what happens to children ordering – gaps that matter for a mutation tool.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, which is good. But for a 0%-documented four-parameter mutation tool, this level of brevity reads as under-specification rather than economy.

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?

An output schema exists so return values need not be explained, but the description leaves essential call information missing: what expected_revision and operation_id mean, what 'explicit' ids must reference, and what the name is applied to. For a non-idempotent mutating tool, this is insufficient.

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?

Schema description coverage is 0% and all four parameters are required, so the description carries the full burden. It only gestures at 'ids' via 'explicit' and at the sibling constraint; name, expected_revision (apparently an optimistic-concurrency token), and operation_id (apparently an idempotency/dedup key) are entirely unexplained.

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 verb+resource is present ('group ... instances'), and 'root-level sibling' narrows the target set, which helps distinguish it from sketchup_combine/transform siblings. However, it never says what the resulting group is (new group entity in the model? named container?) or why one would group rather than combine, so the purpose remains only partly pinned down.

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 statement of when to use this versus sketchup_combine, sketchup_create, or sketchup_transform, and no prerequisites or exclusions. The only implied guidance is that the instances must be root-level siblings, which is a constraint rather than usage routing.

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