Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

project_update

Destructive

Update architectural regions, relations, and models while preserving revision history; specify expected revision, changes, and reason. Dimensions use metres.

Instructions

Update current regions/relations/models, retaining revision history. Dimensions use metres.

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>",
      "changes": "<changes>",
      "reason": "<reason>"
    },
    "name": "project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
changesYes
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 and idempotentHint=false, so the risk profile is known; the description usefully adds that revision history is retained (partial undo capability) and states the unit convention in metres. It does not disclose what happens on a revision mismatch, whether updates are atomic, or which concurrent writers are rejected, which is the key behavior for a destructive non-idempotent tool.

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 padding; the mutation intent leads and the unit convention trails as a useful footnote. Brevity here works against it only in that there is no room left for the payload structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Placeholder — recomputed below.

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. The description says nothing about `expected_revision` (optimistic concurrency token), what keys `changes` accepts despite it being a nested free-form object, or what `reason` is used for; "revision history" only tangentially gestures at the first. This leaves the most consequential parameter effectively undocumented.

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?

The verb+resource framing ("Update current regions/relations/models") identifies this as a mutation of project content and distinguishes it from project_get/project_init. However, "regions/relations/models" is unexplained jargon and the notion of "current" project is never anchored, so an agent cannot say precisely what domain objects get touched.

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 guidance on when to use this versus project_init (first-time setup) or the sketchup_* editing family, nor on prerequisites such as needing an existing project or a current revision. The only implied usage cue comes from the word "Update".

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