Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_undo

Destructive

Revert a SketchUp operation in a distinct event-loop turn, then query and compare revisions to verify rollback success.

Instructions

Undo across a distinct native event-loop turn, then query/compare the result.

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

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

C2.7/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. The description does add real context beyond them – that the undo is issued across a distinct native event-loop turn and that the result is queried/compared afterwards – but it omits what the undo affects, whether the result object reports success/revision drift, and what happens if expected_revision no longer matches. No contradiction with annotations.

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. The 'query/compare the result' clause is the only part that is fuzzy rather than informative, but nothing 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?

An output schema exists, so return values need not be explained, but the tool is destructive, non-idempotent, and has two undocumented required parameters at 0% schema coverage. The description does not say what the revision check protects against or how failures surface, so an agent cannot safely call it.

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% and both parameters are required, so the schema gives no meaning at all. The description never mentions expected_revision (evidently an optimistic-concurrency guard) or operation_id (evidently a dedupe/idempotency token, despite idempotentHint=false). This is a significant gap the description entirely fails to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the verb (undo) but leaves the scope ambiguous – it never says what is undone (last operation, a specific operation via operation_id, history depth). The trailing 'then query/compare the result' is vague about whether this tool returns verification data or performs a comparison itself. An agent can guess it is a sketchup undo but cannot tell it apart from siblings like sketchup_restore_opening on the basis of this text.

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 when-to-use guidance, no prerequisites, and no named alternative for the reverse direction (redo, restore, reopen). Nothing tells the agent when this tool should be preferred over sketchup_restore_opening or sketchup_reopen.

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