Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_probe_pushpull

Destructive

Temporarily push or pull an upward native face to test geometry changes, then undo separately and verify restoration before saving.

Instructions

Temporarily push/pull a real upward native face. Undo in a separate call and verify restoration before saving.

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": {
      "id": "<id>",
      "distance_m": "<distance_m>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>"
    },
    "name": "sketchup_probe_pushpull"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
distance_mYes
operation_idYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior4/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 risk profile is known. The description still adds real value beyond them: the mutation is intended to be temporary, reversal requires a distinct tool call, and restoration must be verified before saving — otherwise the change is persisted. Return format is left to the output schema.

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, front-loaded sentences with no filler and the operational warning placed before the save step. Brevity tips into terseness, though: 'upward native face' is unexplained jargon an agent must guess at.

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 output schema and annotations cover the return shape and risk level, but for a destructive, non-idempotent four-parameter mutation the description is under-specified. It says nothing about what expected_revision and operation_id must contain, what happens if the revision is stale, or how the caller confirms the geometry was restored. The workflow instruction partially compensates but leaves the call mechanics unclear.

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?

All four parameters (id, distance_m, expected_revision, operation_id) are required with 0% schema description coverage, so the description carries the full burden and does almost nothing. Only 'distance_m' is loosely implied by 'push/pull'; expected_revision (concurrency guard) and operation_id (idempotency/correlation) are completely unexplained, and the units/direction of distance are ambiguous despite the word 'upward'.

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 states a specific verb and resource: push/pull a real native face, qualified by 'temporarily'. That is materially clearer than the name alone. It does not distinguish this probe from siblings such as sketchup_transform or sketchup_edit_context, which could also alter geometry, so it stops short of a 5.

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 sequence ('Undo in a separate call and verify restoration before saving'), which implies this is a throwaway probe rather than a committed edit. However, it never says when to choose this over a real transform/edit tool, nor any precondition such as requiring an active selection or an existing face.

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