Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_save

Destructive

Saves the authoritative current SketchUp document to a specified path without overwriting existing outputs, using an expected revision and operation ID to guard against conflicts.

Instructions

Save the authoritative current document; another existing output is never overwritten.

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_save"
  }
}

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, idempotentHint=false and readOnlyHint=false, so the description's added value is the guarantee that a *different* existing output is never overwritten — useful scoping of the destructive behavior. However it never addresses the riskiest aspects: what happens to the current document's prior contents, or why expected_revision and operation_id exist given idempotentHint=false.

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 no filler, and the non-overwrite guarantee is placed prominently. It is arguably too terse for a destructive three-parameter save, but nothing written is wasted.

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?

Return values are covered by the output schema, so the description needn't explain them. But for a destructive, non-idempotent write with three undocumented required parameters, the definition leaves an agent unable to know how to supply expected_revision or how operation_id affects retry behavior.

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% for all three required parameters, and the description compensates for none of them. The meanings of expected_revision (a concurrency/optimistic-locking token) and operation_id (apparently an idempotency/dedup key) are left entirely to inference, which is a serious gap for a required-parameter mutation.

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 and resource ("Save the authoritative current document"), and the qualifier "authoritative current" distinguishes it from merely writing out a derived artifact such as an export. It does not name which sibling to use for alternate persistence paths, but the core action is unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of when this should be preferred over sketchup_export or sketchup_state. The clause about not overwriting another existing output is a behavior note, not a usage routing rule.

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