Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_opening

Destructive

Cut a defined void only into specified actual hosts, saving original host and post-state data for guarded restoration.

Instructions

Cut only specified actual hosts. Stores original hosts and post-state for guarded restoration.

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": {
      "host_ids": "<host_ids>",
      "void": "<void>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_opening"
  }
}

Input Schema

NameRequiredDescriptionDefault
voidYes
host_idsYes
operation_idYes
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?

The annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent, so the safety profile is structured. The description adds genuine context beyond that: it mutates only the explicitly listed hosts and it persists the original host state plus post-state so the operation can be restored. It stops short of disclosing revision-conflict behavior or what happens when a host is ineligible.

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 no filler, and the scoping constraint is front-loaded. The brevity is appropriate, though the second clause is dense enough that it reads as jargon without unpacking.

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, four-required-parameter mutation with zero schema coverage, the description leaves the agent guessing about three of four parameters, including the concurrency token that guards against stale writes. The presence of an output schema removes the need to describe return values, but the input-side burden is unmet.

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%, so the description must compensate and it largely does not. 'Specified actual hosts' partially explains host_ids, but void (box/prism geometry), expected_revision (optimistic concurrency token), and operation_id are entirely unaddressed in both the schema and the description.

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 says it will 'cut' on 'specified actual hosts', which combined with the tool name sketchup_opening implies cutting an opening/void into host elements. However, it never names the resource being created (an opening) or clarifies that the 'void' parameter defines its geometry, so the verb+object pairing remains only partially explicit.

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?

'Cut only specified actual hosts' implies a constraint on which elements are eligible, but there is no explicit when-to-use guidance, no statement of preconditions (e.g. a valid revision), and no reference to the available sibling sketchup_restore_opening as the undo path, even though the phrase 'guarded restoration' gestures at one.

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