Craft Quantities: construction material calculators

Corner trim on your saw: mitre, bevel, stops and the gap

trim_corner

Read-onlyIdempotent

Cuts one corner of skirting, casing or crown molding on a named saw: per piece the mitre and bevel as its dials read, the stop each sits on, how the piece lies, which side to keep, whether the saw can make it; cope or mitre, and the gap a 45° cut leaves. No sizing.

Input Schema

Name	Required	Description	Default
`saw`	No	The saw from the site's library (each with its scale, its stops and its capacity); custom with customSaw. Left out, the 12-in double-bevel slider (DWS779 figures).
`trim`	Yes	skirting (baseboard), casing (architrave, a frame corner) or crown (cornice).
`depth`	No	The depth the joint runs across in the plane of the turn: a skirting's thickness, a casing's face width, a crown's projection. Left out: 18 mm, 70 mm or 75 mm (3/4, 2 3/4 or 3 in).
`corner`	No	The corner as measured. For casing, the frame corner (90 for a square opening); its kind is ignored.
`detail`	No	full (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.	full
`height`	No	Skirting only: its height, for the saw's upright capacity. Left out, 120 mm (4 3/4 in).
`method`	No	How 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.
`spring`	No	Crown only: its spring angle from the wall, degrees (38 for 38/52, 45 for 45/45). Left out, 38.
`system`	No	The unit system inputs left out open in, and the one the page link opens in. The answer comes in both.	metric
`buildUp`	No	Plaster or compound built up in the corner (it changes the angle the trim meets). Left out, none.
`feather`	No	The distance that build-up is feathered over along each wall. Left out, 150 mm (6 in).
`customSaw`	No	With saw custom: the saw's own limits.
`inputUnits`	No	Send "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.
`throughRoom`	No	In place of corner: the angle read through the room (under 180 inside, over 180 outside), as the miter-angle calculator takes it.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world, so the description is free to add what the annotations can't: that the model refuses work outside its scope ('No sizing'), that the answer is returned in both unit systems, and that a summary detail mode exists to save tokens. No auth, rate-limit or persistence behavior is mentioned, but a pure calculator likely has none.

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?

One dense sentence, front-loaded with the verb and resource, with the exclusion pushed to the end for emphasis. The semicolon chain of outputs is compact, though the list of returned fields is packed tightly enough to need a second read.

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 14 parameters, full schema coverage, an output schema and strong annotations, the description only needs to frame the job and scope, which it does. It could say more about the returned feasibility/capacity verdict, but the output schema carries that detail.

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 coverage is 100% and the per-field descriptions are already detailed with defaults and units, so the description adds little parameter-level meaning. It does frame the answer content ('cope or mitre, and the gap a 45° cut leaves'), but no syntax or unit behavior is explained beyond what the schema states.

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 (cuts) and resource (one corner of skirting/casing/crown on a named saw) and enumerates what comes back: mitre/bevel dial readings, stop, piece orientation, keep side, feasibility, cope-vs-mitre, gap. The closing 'No sizing' also marks it off from sizing/planning siblings.

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?

Implies the use case (a single corner on a specified saw) and excludes sizing work, but never names an alternative such as miter_chart or plan_room_trim, nor states when to prefer those. Usage has to be inferred from the purpose statement.

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

All Craft Quantities: construction material calculators tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?