Skip to main content
Glama

Measure the plan

measure
Read-only

Measure distances, gaps, and free floor space between objects or along axes in a floor plan, and determine how large a piece can grow before hitting obstacles.

Instructions

Tape measure over the plan, in cm. from= alone: free floor on all four sides, {clear:{"+y":[cm,id,name]}} — dirs picks sides (+x -x +y -y, or front/back/left/right of the piece). from+to (ids or [x,y]): the distance between them, {cm}, or the gap along axis. axis+at: what a straight probe runs into, {spans:[[from,to,id,name]]} with id null for free floor — the answer to "how wide is the corridor here, and between what". Add gap= and grow= and it also answers how big that piece can be along the axis before the gap is broken, and what stops it there: {fit:{free,max,blocked_by}} — the question a layout decision actually ends in, without trying a size and undoing it. z limits the height band that counts (default 0-200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zNoHeight band that counts, `[z0, z1]` cm above this storey's floor. Default `[0, 200]`: what a person walking through meets
atNoProbe line: with `axis`, the other axis' coordinate. Reports every stretch a straight line crosses, free floor and solids alike
toNoWhat to measure to: an id or `[x,y]`
gapNoWith a probe: how much free floor has to be left along it, cm
axisNoRestrict to one axis, `x` or `y`. Between two boxes this is the gap along that axis (negative when they overlap)
dirsNoSides to measure free floor on: `+x`, `-x`, `+y`, `-y`, or, relative to the piece, `front`, `back`, `left`, `right`
fromNoWhat to measure from: an id or `[x,y]`. Alone, reports the free floor on all four sides of that piece. Openings instead report wall-axis spans, distances to wall ends and neighboring openings; no floor clearances
growNoWith a probe and `gap`: the piece that would grow. The answer says how big it can be along the axis and what stops it there
rangeNoLimits of the probe along `axis`, `[from, to]` cm. Default: the plan

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoGap along x, cm
yNoGap along y, cm
cmNoDistance, cm
idNoThe element measured
fitNoProbe with gap: {free, max, blocked_by}
axisNoAxis measured along
clearNoFree floor by side: [cm, against id, name]
facesNoSide its front looks to
spansNoProbe: [from, to, id, name] along the axis
boundsNoThe piece's [[minx,miny],[maxx,maxy]] cm
openingNoA door or window: {basis, hosts}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark the tool read-only; the description adds useful behavioral detail about result shapes ({clear}, {spans}, {fit}), what counts as free floor, and the default z height band. It does not contradict the annotations and goes beyond what they convey.

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 dense and telegraphic, yet every clause carries information about a mode or result. The single-paragraph structure and compact pseudo-JSON examples reduce scannability, but there is no filler and the core purpose is front-loaded.

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 a 9-parameter, multi-mode measurement tool with an output schema, the description covers the main invocation intents and their result semantics well enough for correct use. It is slightly less complete on error/edge cases like combining mutually exclusive modes, but the schema and optional parameters mitigate that.

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 the baseline is 3, but the description adds real combination semantics: dirs picks sides, gap+grow produces a fit answer, axis+at returns spans, and z bounds the analyzed height band. It does not mention the range parameter, but the schema fully documents that parameter.

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 opening 'Tape measure over the plan, in cm' plus the enumerated modes (from-alone free floor, from+to distance, axis+at probe spans, gap+grow fit) makes the tool's purpose concrete and distinguishable from sibling design/editing tools. It does not explicitly name a sibling it is not, so it falls short of a 5.

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?

The description gives explicit mode-selection conditions: 'from=<id> alone', 'from+to', 'axis+at', and 'Add gap and grow', which tells an agent which parameter combination is appropriate for which measurement intent. It does not name alternatives or state when not to use the tool, so it misses the top of the scale.

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