Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_new

Destructive

Create a new saved workspace document in SketchUp after preserving current unsaved work. Prevents data loss by safeguarding edits before starting a fresh model.

Instructions

Create a new saved workspace document only after preserving any current 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_new"
  }
}

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

C2.9/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 structurally. The description adds a corroborating warning that unsaved work is at risk, but it does not say what exactly is destroyed or replaced, how the expected_revision guard behaves on mismatch, or why operation_id exists despite the tool not being idempotent.

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 sentence with no padding, and the precondition is placed after the core action so the purpose lands first. Its brevity is efficient but borders on under-specification for a destructive three-parameter tool.

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?

The tool is destructive, takes three undocumented required parameters, and creates durable state, yet the description covers only the headline action plus a vague warning. With no output-schema explanation needed, the missing pieces are the mutation semantics, revision-guard behavior, and operation_id purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three required parameters (path, expected_revision, operation_id) have 0% schema description coverage, so the description carries the full burden, and it explains none of them. It adds no meaning about path format, revision/concurrency semantics, or the purpose of the operation_id correlation key.

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: 'Create a new saved workspace document.' An agent can tell this is a document-creating operation, though it never says what kind of document (a SketchUp model?) and never contrasts it with siblings like sketchup_open, sketchup_create, or sketchup_save.

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?

'Only after preserving any current unsaved work' states a precondition for calling the tool, which is useful usage guidance. However, it offers no routing guidance between this tool and the plausible alternatives (sketchup_open, sketchup_create, sketchup_restore), and no explicit when-not conditions.

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