Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_reopen

Destructive

Reopen a saved workspace model only when no unsaved edits exist in the native window, then export and compare results against the expected revision.

Instructions

Reopen a saved workspace model only when the native window has no unsaved edits, then export and compare.

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

Input Schema

NameRequiredDescriptionDefault
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered upstream. The description adds the unsaved-edits guard and hints at composite side effects ('export and compare'), but leaves ambiguous what is overwritten, whether the export/compare is part of this call or a separate step, and what happens if the guard is violated.

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 wasted words, and the critical precondition sits before the follow-on actions. The density is slightly too high for the ambiguity it creates around the export/compare tail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 described, and there are only two parameters. Still, a destructive, non-idempotent operation with entirely undocumented parameters and an unexplained composite behavior leaves gaps an agent would have to guess at before calling 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 both parameters (operation_id, expected_revision) are undocumented anywhere. The description must compensate and does not: expected_revision in particular looks like a concurrency guard whose semantics an agent needs, and neither parameter is mentioned.

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 states a specific verb and resource ('Reopen a saved workspace model'), which reads distinctly from a fresh-open tool. However, the trailing 'then export and compare' muddies the core purpose: it is unclear whether this tool is a reopen operation or an export/compare pipeline, and no sibling is named to sharpen the distinction.

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

Usage Guidelines4/5

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

A concrete precondition is given ('only when the native window has no unsaved edits'), which tells the agent when the tool is valid. It stops short of naming alternatives such as sketchup_open or sketchup_restore_opening, and it does not say what to do instead when the precondition fails.

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