Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

sketchup_delete

Destructive

Delete declared SketchUp objects and report preserved or replaced enclosure, support, and protection, then recheck old openings and finishes.

Instructions

Delete declared objects. Explain preserved/replaced enclosure, support and protection; recheck old openings and finishes.

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": {
      "ids": "<ids>",
      "expected_revision": "<expected_revision>",
      "operation_id": "<operation_id>",
      "functional_reason": "<functional_reason>"
    },
    "name": "sketchup_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
scene_namesNo
operation_idYes
expected_revisionYes
functional_reasonYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior4/5

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

The annotations already declare destructive=true and idempotent=false, so the basic risk profile is covered. The description adds useful domain context by warning that deletion has architectural consequences for enclosure, support, protection, old openings, and finishes. It still does not explain cascade behavior, authorization, or how revision conflicts are handled.

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?

The description is only two sentences and front-loads the action, with no filler or repetition. The second sentence is terse and somewhat cryptic, but it is not verbose.

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?

For a destructive five-parameter tool with a required revision, operation ID, and functional reason, the description is too thin. It adds dependency-check guidance but leaves parameter meaning, concurrency expectations, and deletion scope unexplained, even though the output schema means return values need not be described.

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?

Schema description coverage is 0%, and the description does not explain any of the five parameters, including the required ids, expected_revision, operation_id, and functional_reason. The phrase "declared objects" only vaguely suggests ids and leaves the revision, operation, and reason fields 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 states a clear verb and resource: "Delete declared objects." It is specific enough to distinguish deletion from creation, editing, or querying, but it does not clarify what object types are eligible or differentiate this tool from siblings such as sketchup_edit_context or sketchup_opening.

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?

The description gives post-deletion checks involving enclosure, support, protection, openings, and finishes, but it does not say when to use this tool versus alternatives or when deletion is inappropriate. The guidance is dependent-action oriented rather than selection oriented.

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