Craft Quantities: construction material calculators

Full-size print template as SVG and DXF

print_template

Read-onlyIdempotent

The full-size template a calculator page prints: a stair stringer or step gauge, rafter cuts, a cone or frustum pattern, an arch's centring or voussoirs, an anchor bolt setting jig or plate, a curved plate; its lines as SVG and DXF, its checks and omissions, and how it tiles on paper.

Input Schema

Name	Required	Description	Default
`kind`	No	Which of the family's two templates: stringer gauge or whole; rafter cuts or whole; cone whole or half; arch centring or voussoirs; bolts setting or plate; plate segment or whole. Left out, the first.
`paper`	No	Left out, A4 for metric and Letter for imperial.
`detail`	No	full (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.	full
`fields`	No	The template's own figures by id (a stringer's board depth and tread thickness, a cone's lap …), with units; left out, the page's defaults for the system (or the calculator's own figure where the page opens on it). The answer lists them.
`inputs`	No	The calculator's own inputs by id, with their units, as its page takes them; left out, the values its page opens on.
`system`	No	The unit system inputs left out open in, and the one the page link opens in. The answer comes in both.	metric
`formats`	No	The drawings to return. Left out, both.
`overlap`	No	Between adjacent sheets. Left out, 10 mm.
`rollWidth`	No	With paper roll: the roll's width.
`calculator`	Yes	The calculator whose page offers the template: a stair stringer and step gauge, a rafter, a cone or frustum pattern, a curved wall's plate, an anchor bolt setting board or plate, an arch's centring or voussoirs.
`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.
`orientation`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds that the output includes lines as SVG and DXF, checks and omissions, and paper tiling behaviour, which is useful beyond annotations, but it does not describe error behavior, performance, or how the template is generated.

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 a single front-loaded sentence that immediately identifies the resource. It is somewhat list-heavy and repeats template types that also appear in the calculator and kind schema descriptions, but it remains appropriately sized and does not contain wasted framing.

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?

Given an output schema and rich annotations, the description does not need to explain return values or safety properties. It sufficiently covers scope, output formats, checks/omissions, and paper tiling for a 12-parameter read-only generation tool, though it could be more complete on when to choose it over related drawing tools.

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 92%, so most parameter semantics are already documented in the schema. The description adds little parameter-level detail beyond mentioning SVG/DXF lines and tiling on paper, so the baseline of 3 is appropriate.

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 description states a specific resource — the full-size printable template produced from a calculator page — and lists example template families (stair stringer, rafter cuts, cone pattern, arch centring, anchor bolt jig, curved plate). It does not explicitly distinguish itself from sibling drawing tools such as create_drawing or export_drawing, so sibling differentiation is absent.

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?

Usage is implied by 'the full-size template a calculator page prints', suggesting it is used after or alongside calculator results. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives among the many drawing/template siblings.

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?