Skip to main content
Glama

Craft Quantities: construction material calculators

Plan the materials for one room or space

plan_room
Read-onlyIdempotent

Plans one space, such as a room or a bathroom, from its size, openings and the finishes chosen, as the site's room planner does, and returns its materials list: each row with its quantity, what it still needs, what is not built and why, and labour hours. Quantities only; it does not size structure.

Input Schema

NameRequiredDescriptionDefault
kindYesThe kind of space: a room or a bathroom (from its size, doors and windows), or a slab, deck, driveway, fence, loft, retaining wall, exterior wall or stair.
nameNo
doorsNo
scopeNoScope question name → answer value, by the planner's ids.
detailNofull (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.full
inputsNoBranch id → { calculator input id: value in its base unit }.
intentNoA trade, or everything.
systemNoThe unit system inputs left out open in, and the one the page link opens in. The answer comes in both.metric
figuresYesThe space's figures, by the planner's ids, each a length with its unit (a room: length, width, height, wallThickness; a fence: length, height; a stair: totalRise, width …).
windowsNo
finishesNoSurface role → finish id, by the planner's ids.
leaveOutNoBranch ids to leave out.
inputUnitsNoSend "base" to pass bare numbers on dimensioned inputs in base units (m, m², L, kg …), as the published test vectors are written. Without it a length, area or volume must carry its unit.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds value beyond that by spelling out the return contents and asserting a hard scope boundary: 'Quantities only; it does not size structure,' which tells the agent what this tool will not produce.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and immediately followed by the output contract and the scope caveat. No filler and every clause carries information.

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?

An output schema exists, so return values need no further elaboration, and annotations cover the safety profile. The description supplies the scope limit and output summary; only fine-grained guidance on the 13 parameters is thin, and the schema largely covers that.

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

Parameters3/5

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

Schema description coverage is 77% and 13 parameters are documented in the schema itself. The description only gestures at the input dimensions ('its size, openings and the finishes chosen'), loosely mapping to figures, doors/windows and finishes, without adding format, unit or id-semantics detail beyond the schema. Baseline 3 is appropriate.

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 (Plans) and resource (one space such as a room or bathroom) and describes the output shape in detail (materials list rows with quantity, remaining needs, unbuilt items and reasons, and labour hours). The scope is narrow enough to separate it from the project-level sibling plan_project without opening either schema.

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

Usage Guidelines3/5

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

The 'one space' framing implies when to use it versus a whole-project planner, but no alternative is named and there are no explicit when/when-not conditions or prerequisites. Usage is inferable but not stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources