Skip to main content
Glama
Meteor-Simulation

BULC MCP

Official
by Meteor-Simulation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Arch import floorplan report

arch_import_floorplan_report
Destructive

Create walls, doors, and windows from a floor-plan image or outlined PDF page to build BULC fire-simulation geometry.

Instructions

Build walls / doors / windows from YOUR reading of a floor-plan picture (image or outlined PDF page — use when arch_analyze_drawing says needsVision). report = {building_width_m (real width of the outer walls), wall_height_m?, wall_thickness_m?, walls:[{x1,y1,x2,y2}] wall CENTRELINES in normalised image coordinates 0..1 (origin top-left, y down; split at corners, skip dimension lines, text, furniture, hatching), doors:[{x,y,width_m?}], windows:[{x,y,width_m?,sill_m?,height_m?}]}. image = {width,height} pixels (or imagePath) for the aspect ratio. The app converts the report with fixed rules (snap to horizontal/vertical, y flipped, origin at the lower-left wall corner) and creates the same objects as arch_import_building. Needs no AI key in the app. dryRun defaults to TRUE. [bulc-mcp rules] DRW-008, DRW-004 — bulc_knowledge_search ""

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
imageNoImage size in pixels
storyNo
zBaseNo
dryRunNoOnly report (default TRUE)
reportYesFloor-plan report (see description)
includeNoWhat to create: doors (true), windows (true), columns (true), floorSlab (false — slab just below the story floor), ceilingSlab (false — slab on top of the walls)
defaultsNowallHeight (default: story height), wallThickness (walls without one, default 0.2), doorWidth 0.9, doorHeight 2.1, windowWidth 1.2, windowSill 0.9, windowHeight 1.2, slabThickness 0.2 (m)
idPrefixNo
imagePathNoAbsolute path of the image (its header gives the size)
transformNoPlacement: origin = 'bbox_min' (default for drawings: lower-left corner of the building) | 'none' | [x,y] in drawing metres; target [x,y] (default [0,0]); rotateDeg about the target (counter-clockwise); mirrorY. Use the same origin for every story drawing of one building.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false. The description adds genuinely useful behavior beyond that: dryRun defaults to TRUE, the app converts the report with fixed rules (snap to H/V, y-flip, lower-left origin), and no AI key is required. It does not spell out what 'replace' destroys or auth requirements, so it is not a 5.

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?

Dense but front-loaded, leading with the purpose and activation condition before the report schema. It is long and run-on in places, but nearly every clause (coordinate origin, y direction, dryRun default, conversion rules) carries information an agent needs, so little is wasted.

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

Completeness4/5

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

For an 11-param mutation tool with nested objects and no output schema, the description covers the hard parts: the report contract, coordinate conventions, dry-run safety, conversion semantics, and placement defaults. Gaps remain around the append/replace mode effect and story/zBase implications, but the definition is largely self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 64% schema coverage, the description meaningfully compensates: it fully specifies the required 'report' payload (fields, units, coordinate convention, splitting at corners, what to skip), the image aspect-ratio param, and the transform origin/target/mirrorY semantics. A few params (mode, story, zBase, idPrefix) get no description-level elaboration.

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

Purpose5/5

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

States a specific verb+resource ('Build walls / doors / windows from YOUR reading of a floor-plan picture') and immediately names the trigger ('use when arch_analyze_drawing says needsVision'). It also ties itself to the sibling arch_import_building ('creates the same objects as arch_import_building'), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit activation condition ('use when arch_analyze_drawing says needsVision') and clarifies the app needs no AI key, which frames the division of labour with the vision path. It stops short of an explicit when-not (e.g., when to prefer arch_import_building), but the routing context is clear.

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

Deploy Server

Other Tools