Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_restore_opening

Destructive

Restores recorded host geometry for an opening only if the post-cut host is unchanged, preventing unsafe rollback when the model has been modified.

Instructions

Restore recorded host geometry only if the post-cut host has not changed.

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": {
      "opening_id": "<opening_id>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_restore_opening"
  }
}

Input Schema

NameRequiredDescriptionDefault
opening_idYes
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructive=true, idempotent=false, and readOnly=false, so the safety profile is covered elsewhere. The description adds the meaningful safety guard about host staleness, but does not disclose what happens on mismatch (error vs. silent skip), whether partial restores are possible, or whether the destructive write is reversible.

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?

One sentence with no padding, and the conditional guard is front-loaded where it matters. The brevity shades into under-specification given three undocumented parameters, but nothing is redundant.

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 and annotations exist, so return values and safety need not be restated. Still, for a destructive three-parameter restore with 0% schema coverage and a stated staleness check, the description omits the failure semantics and parameter roles an agent needs to invoke it safely.

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 three required parameters (opening_id, expected_revision, operation_id) carry no documented meaning in either place. The description hints at a revision check but never connects expected_revision to that guard, nor explains what operation_id is used for, leaving the schema gap uncompensated.

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?

States a specific verb (restore) and object (recorded host geometry), plus a guard condition, which is more than a tautology. However, terms like 'host geometry' and 'post-cut host' are domain jargon that an agent cannot resolve from the text, and nothing distinguishes this from siblings such as sketchup_opening or sketchup_undo.

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

Usage Guidelines3/5

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

The clause 'only if the post-cut host has not changed' functions as a precondition for use, which is genuine guidance. But it names no alternative for the changed case, gives no fallback or recovery path, and offers no reason to pick this over sketchup_undo or sketchup_reopen.

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