Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_combine

Destructive

Combine explicit solid instances into a single union while preserving cavities and replacing inputs transactionally.

Instructions

Union explicit solid instances; preserves actual cavities. Inputs are replaced transactionally.

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_combine"
  }
}

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

B3.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value beyond them: 'preserves actual cavities' discloses geometric semantics, and 'Inputs are replaced transactionally' discloses that the source objects are consumed and the operation is atomic. It does not explain failure/rollback behavior for the non-idempotent case.

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 tight sentences that front-load the operation and then the two behavioral guarantees. Minimal waste, though 'explicit' and 'actual' are vague qualifiers that add words without adding 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?

An output schema exists, so return values need no explanation, but this is a destructive, non-idempotent operation with four undocumented required parameters. An agent cannot learn from the description why expected_revision or operation_id are mandatory, which is essential to calling it correctly.

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% across four required parameters, and the description never mentions ids, name, expected_revision, or operation_id. 'Inputs are replaced' only obliquely gestures at what ids means; the concurrency token and idempotency key are entirely unexplained, so the description fails to compensate for the coverage gap.

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 gives a specific verb and resource: 'Union explicit solid instances' tells the agent this is a boolean-union combine operation over solid geometry, which is distinguishable from siblings like sketchup_group or sketchup_transform. The word 'explicit' is left unqualified, so the precondition on inputs remains fuzzy.

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 stated when-to-use versus alternatives (e.g. grouping vs unioning with sketchup_group), and no prerequisites such as the inputs needing to be manifold solids. The only implied constraint is 'explicit solid instances', which the agent must guess at.

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