Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
blenderNoPath to the Blender executable (passed as --blender /absolute/Blender) when Blender is not in the default location.
workspaceYesThe project working directory to connect to (passed as --workspace /absolute/project). Required to run `python -m amw.cli serve`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read project and active document state first. User chooses schemes and major spatial changes. Never interpret a file fingerprint as a geometry or whole-building certificate. All exchange coordinates are metres.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_capabilitiesA

Inspect actual software connection, units, stages and validation limits.

project_initC

Create one current fact record; existing projects are never overwritten.

project_getA

Read current facts, decisions, checks, pending issues and revision.

project_link_authorityC

Link an existing JSON fact table as sole semantic authority. Refresh only after reading/reconciling its actual changes.

project_updateC

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

decision_recordB

Record the actual user decision with a retrievable source; never invent user approval.

stage_checkC

List stage conditions, stale evidence and required user decisions.

stage_advanceB

Advance one stage only after evidence and design decision conditions are met.

stage_reopenC

Return to an affected earlier stage without erasing facts or old evidence.

evidence_registerC

Read and bind a real scoped report and its current source files. Does not prove its assertions.

sketchup_stateB

Inspect actual document identity, unsaved changes, disk drift, scene and live revision.

sketchup_newC

Create a new saved workspace document only after preserving any current unsaved work.

sketchup_openB

Open a saved workspace document; refuses to switch away from unsaved work.

sketchup_queryC

Find native instances and identities without dumping all geometry. Use IDs for editing.

sketchup_createC

Create one editable native solid. Floor polygon Z is its structural bottom; choose finished-face conventions explicitly.

sketchup_transformC

Apply a world-space column-major affine matrix once; translation is metres.

sketchup_deleteC

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

sketchup_materialC

Assign a local material without recoloring unrelated users of an existing material.

sketchup_openingC

Cut only specified actual hosts. Stores original hosts and post-state for guarded restoration.

sketchup_restore_openingC

Restore recorded host geometry only if the post-cut host has not changed.

sketchup_combineB

Union explicit solid instances; preserves actual cavities. Inputs are replaced transactionally.

sketchup_groupC

Group explicit root-level sibling instances without boolean rebuilding their geometry/materials.

sketchup_scriptA

Run trusted workspace Ruby inside a native transaction. Do not manage transactions or change documents/edit context in scripts. Declare existing geometry scopes, any new roots and scene names. This is code execution, not an OS sandbox.

sketchup_saveC

Save the authoritative current document; another existing output is never overwritten.

sketchup_edit_contextA

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.

sketchup_undoC

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

sketchup_reopenB

Reopen a saved workspace model only when the native window has no unsaved edits, then export and compare.

sketchup_probe_pushpullB

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

sketchup_exportC

Export actual world geometry, native face rings, UV, materials, instance paths and scenes.

sketchup_captureC

Capture the actual current native view for visual review; an image is not a geometry certificate.

sketchup_sceneC

Select an existing scene or save one explicitly requested camera; does not create diagnostic scene clutter.

sketchup_importB

Import a workspace asset through SketchUp's native importer; inspect units and editability afterwards.

native_job_statusC

Resume the same native operation; never create a second write after a timeout.

native_job_cancelB

Cancel a queued operation. Running native transactions finish atomically.

asset_buildB

Create/continue an independent editable Blender asset. Supply asset_id, new blend/glb/dae/preview paths, parts or trusted script, anchor and license sources.

asset_job_statusB

Return durable worker status, Blender exit code and saved/reimport verification.

asset_job_cancelB

Cancel only this server-owned Blender worker group; incomplete outputs are invalid.

checks_runC

Compute actual geometry checks. Inputs are IDs/contours/routes and project dimensions, not preset compliance rules.

evidence_inheritC

Inherit only a check whose declared dependencies are actually unchanged and semantic basis is unchanged. Missing dependencies cannot be guessed.

drawing_read_sliceC

Read handoff geometry into a plan/section cut-segment draft; final drawing stays in the next workflow.

handoff_exportB

Freeze a stage-approved handoff with source hashes, actual geometry and explicit unverified scope.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
current_project

TDQS

C2.8/5.0

Scored across 41 tools

Disambiguation4/5

Most tools target distinct resources and actions, with clear domain prefixes separating project, SketchUp, asset, evidence, and job operations. A few read/inspect/export tools overlap conceptually (project_get vs sketchup_state vs get_capabilities; sketchup_export vs handoff_export), but descriptions generally clarify boundaries.

Naming Consistency4/5

The set overwhelmingly follows a snake_case resource_action pattern (project_get, sketchup_create, stage_advance, evidence_register), which is predictable despite not being verb_noun. Occasional outliers like get_capabilities and mixed noun/verb phrasing keep it from a 5.

Tool Count2/5

The domain is broad and many tools are specialized, but 41 tools is heavy and exceeds a practical set size. Several low-level SketchUp operations and status/cancel pairs could likely be consolidated without losing capability.

Completeness4/5

The surface covers project lifecycle, stage gates, decisions, evidence, checks, SketchUp modeling/export/save, Blender asset jobs, and handoff. Minor gaps exist around asset inspection/listing and project deletion or archival, but core workflows appear well covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues