Skip to main content
Glama
U-C4N
by U-C4N

Architecture: Label Room

arch_room

Labels the room containing a WCS point with its name, number and area measured from the closed wall faces, net of wall thickness and columns.

Instructions

Label the room around (x, y) with its name, number and MEASURED area.

The area is never typed: the tool reads the wall faces on the wall layer of the arch set (LINE and lightweight polyline, both engines; anything else there is listed in skipped), finds the closed face the point lies in and writes that face's area - net of the wall thickness and of any column inside it - into the label and into an ACADMCP_ARCH room record on the name text, which arch_schedule reads. A door or window recorded on the drawing closes its gap along the wall faces, so two rooms either side of a door stay two rooms.

Refused before anything is drawn: an unknown lang (named with en, tr), a number/name the room model refuses, a room_id already labelled on the drawing, a point in no closed face of the walls (draw or close them first, or read a plan drawn by other means with arch_rooms_detect), a point inside a wall body, and a point in a room that already carries a label (one face, one room record - a retried call does not add a second area to the schedule).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesWCS X of a point inside the room; the label starts here.
yYesWCS Y of a point inside the room.
langNoLabel language: en | tr (tr writes 24,50 m²).en
nameYesRoom name, e.g. LIVING / SALON.
scaleNoPlot-scale denominator: 50 is 1:50 (text x 50).
numberNoRoom number, e.g. 01; omit for none.
room_idNoRecord id; default is the first free R<n>.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the minimal destructiveHint=false annotation by describing exactly how area is computed (reads wall faces on the wall layer, net of thickness and columns), how doors/windows affect room separation, what gets written (label text and ACADMCP_ARCH xdata), and the one-label-per-face idempotency behavior.

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?

Front-loads the action, then explains mechanics, then lists refusals. Slightly long, but every sentence is informative. Minor density could be improved but no wasted sentences.

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?

For a 7-param mutation tool with no output schema in description, all critical aspects (inputs, side effects, downstream consumption by arch_schedule, refusal cases) are covered. Complete enough for an agent to invoke correctly.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: lang values (en, tr) with numeric format example, area is never typed (x,y only), and room_id ties to a record written onto the name text. Adds value beyond schema descriptions.

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 (Label) and resource (the room around x,y) and specifies what the label contains (name, number, MEASURED area). It clearly distinguishes itself from siblings like arch_rooms_detect (read plans drawn by other means) and arch_schedule (reads records).

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

Usage Guidelines5/5

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

Explicitly lists refusal conditions (unknown lang, invalid number/name, duplicate room_id, point in no closed face, point in wall, already labeled room) and points to the alternative arch_rooms_detect for plans drawn by other means. This is thorough when/when-not guidance.

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