Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_open

Destructive

Opens a saved workspace document for continued architectural modeling, and prevents switching away from unsaved work so edits are not lost.

Instructions

Open a saved workspace document; refuses to switch away from unsaved work.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
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
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description contributes a genuinely behavioral detail: it aborts rather than replacing a document with unsaved changes. It does not explain how a revision mismatch or missing file is handled, which matters for a tool with an expected_revision parameter.

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?

A single front-loaded sentence with zero filler; the clause order puts the action before the caveat. It is efficient, though its brevity borders on under-specification given three undocumented parameters.

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 described. But for a destructive, non-idempotent open operation with three fully undocumented required parameters, the definition omits the semantics an agent needs to call it correctly, especially expected_revision and operation_id.

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 three required parameters. The description implies a file path but says nothing about expected_revision (clearly a concurrency/optimistic-locking token) or operation_id (likely an idempotency key). With no schema help, the description should have carried this meaning and does not.

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?

States a specific verb+resource: "Open a saved workspace document." This is clear enough to act on, but it doesn't distinguish opening from sibling tools like sketchup_reopen or sketchup_new, leaving the agent to differentiate by name alone.

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 guard clause "refuses to switch away from unsaved work" implies the precondition for safe use, which is useful context. However, there is no explicit guidance on when to choose this over sketchup_reopen or sketchup_import, and no stated alternative for the unsaved-work case (e.g. save first).

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