Skip to main content
Glama

Craft Quantities: construction material calculators

Room trim plan: every piece, its ends and the stock

plan_room_trim
Read-onlyIdempotent

Plans trim round a room, piece by piece, from its corners, door openings and built-ins (or a drawn room): each piece in fitting order with its long and short point lengths, each end's cope, mitre, butt or scarf with its saw settings, the cut list and the trim lengths to buy.

Input Schema

NameRequiredDescriptionDefault
sawNoThe saw profile the room plan's settings are read on (as the plan on the page): a mitre saw that tilts both ways (the default), one that tilts left only, or a mitre box with 90° at square.
kerfNoThe saw's kerf. Left out, 3 mm (1/8 in).
roomNoWith drawing: the room's id (R1 …). Left out, the drawing's only room.
trimNoLeft out, skirting.
depthNoThe trim's depth across the joint (skirting thickness, crown projection). Left out, 18 mm (3/4 in) or 75 mm (3 in) for crown.
startNoThe wall fitted first (index). Left out, 0.
stockNoThe stock lengths on offer, with units. Left out, the market's usual trim lengths.
studsNo
wallsNoThe walls in order round the room, up to 40, each with its length along the wall face (corner to corner).
casingNoThe door casing's width a skirting butts to beside a door. Left out, none (it butts to the opening's edge).
detailNofull (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.full
methodNoHow the piece goes on the saw: skirting and casing upright (against the fence) or flat (on the table); crown nested (upside down against the fence) or flat. Left out, the trim's usual one.
springNoCrown only: its spring angle from the wall, degrees (38 for 38/52, 45 for 45/45). Left out, 38.
systemNoThe unit system inputs left out open in, and the one the page link opens in. The answer comes in both.metric
buildUpNoPlaster built up in the corners. Left out, none.
cornersNocorners[i] is at the end of walls[i], where it meets the next wall (one per wall; the last closes the room).
drawingNoIn place of walls and corners: a Construction Canvas drawing in any form the drawing tool takes ({ document }, { commands }, { template }, { house }, { shapes }, { layout }); the room's inside faces, corners and doors are read from it as the canvas's Trim plan reads them.
directionNocw (the default): facing each wall from the room, working left to right. ccw: the canvas's order.
minOffcutNoOffcuts at least this long are kept.
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.
insideJointNoInside corners coped (the default) or mitred.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds substantial behavioral detail beyond that: fitting order, long and short point lengths, end treatments with saw settings, cut list, and trim lengths to buy.

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?

It is a single front-loaded sentence, with the colon cleanly separating purpose from output details. It is dense but has little filler; splitting it could improve readability, but it is appropriately sized for a 21-parameter planning tool.

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?

With an output schema, rich annotations, and 95% schema description coverage, the description is complete at the high level an agent needs. It covers the main input modes and outputs, though it does not explicitly state the walls-plus-corners versus drawing input choice or defaults, which the schema handles.

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 95%, so the schema already carries nearly all parameter meaning. The description adds only high-level input modes such as corners, openings, built-ins, and drawn rooms, without adding defaults, unit behavior, or syntax beyond the schema.

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 and resource: plans trim round a room piece by piece from corners, openings, built-ins, or a drawing. The scope and output list distinguish it from a single-corner tool or saw chart, even though it does not name siblings explicitly.

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 description gives a clear planning context, especially for whole-room trim from walls or a drawn room. However, it never says when to choose this over trim_corner, miter_chart, optimise_cuts, or plan_room, so usage is implied rather than explicit.

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