Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_edit_context

Destructive

Switch SketchUp editing context by entering a native instance path or exiting to the root model with a null id, so edits and final saves occur in the correct scope.

Instructions

Enter a native instance editing path, or exit to the model when id is null. Finish any current GUI gesture before changing context; final save requires the root context.

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

Input Schema

NameRequiredDescriptionDefault
idNo
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the description's job is to add context. It does: the GUI-gesture precondition and the root-context requirement for saving reveal ordering constraints an agent would otherwise trip over. It still doesn't say what happens to in-progress state or how context conflicts are reported.

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?

Two short sentences, front-loaded with the primary action and the id-null exit rule. Every clause carries information; the only weakness is the unexplained 'native instance editing path' phrasing.

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 needn't be described. But for a destructive context-switching tool with three parameters and zero schema descriptions, leaving operation_id and expected_revision semantics unstated is a meaningful gap.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry parameter meaning. It explains only 'id' (null means exit to the model); 'operation_id' and 'expected_revision' — including what a revision mismatch does — are left entirely undocumented.

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 names a specific action pair (enter an instance editing path, exit to the model) and ties it to a resource (editing context). It is distinguishable from siblings like sketchup_open or sketchup_group, though the phrase 'native instance editing path' is jargon that is not defined.

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?

It gives a conditional rule (id null = exit to the model) and a precondition ('finish any current GUI gesture') plus an ordering dependency ('final save requires the root context'). However, there is no explicit guidance on when to enter a context versus using another sibling such as sketchup_open or sketchup_transform.

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