Skip to main content
Glama

Craft Quantities: construction material calculators

Roof framing: rafter lengths, cuts, birdsmouth and templates

roof_framing
Read-onlyIdempotent

Lays out a gable or hip roof (optionally a gable wing with valleys) from the caller's own sizes: each common, hip, valley and jack rafter's length along the line, birdsmouth and HAP, plumb and cheek cuts as saw settings, hip backing, a cut list on the caller's stock, and a member's full-size template as SVG and DXF; both systems. Geometry only: it does not size structure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "roof_framing"
  }
}

Input Schema

NameRequiredDescriptionDefault
kerfNoSaw kerf, charged on every cut (default 1/8 in or 3 mm).
kindNogable or hip (default hip).
langNoThe answer's language. en (the default): as ever. es or es-US: US Spanish — labels, units, result lines and the honest machine-translation label from the site's Spanish pages, Spanish words read in a question or a trade term, and links to the /es/ pages once the site publishes them (until then the links stay English). fr or fr-CA (Canadian French, /fr/) and pt or pt-BR (Brazilian Portuguese, /pt/): the same from the site's French and Portuguese pages, figures with a decimal comma; each link names the translated page only once that page is published, otherwise the English page.en
rakeNoGable ends (and a wing's gable end): how far the roof runs past the gable wall.
spanNoBuilding width across the ridge, outside faces of the wall plates ("24 ft", "8 m").
wingNoAn equal-pitch gable wing on the front wall: gives the valleys, valley jacks and cripples.
pitchNoRise per 12 of run (6 for 6/12). Or give pitchDegrees.
stockNoThe stock lengths the caller can buy, each with its unit; left out, the page's list for the system.
detailNofull (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.full
hipTopNoDrop the hips and leave them square (default), or back them.
lengthNoBuilding length along the ridge.
systemNoThe system figures are read in and printed first (both are returned).metric
spacingNoRafter centres along the plate ("16 in", "600 mm").
hipDepthNoActual depth of the hips and valleys.
overhangNoLevel, from the wall's outer face to the tail's plumb cut.
templateNoOne member as a full-size template (1:1, millimetres).
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.
plateWidthNoThe wall plate's width (the seat bears on it).
rafterDepthNoActual depth of the commons and jacks (a 2×8 is "7.25 in").
hipThicknessNoActual thickness of the hips and valleys.
pitchDegreesNoThe pitch in degrees, as an alternative to pitch.
ridgeThicknessNoThe ridge board's thickness.
fasciaThicknessNoThe fascia board's thickness.
rafterThicknessNoActual thickness of the commons and jacks ("1.5 in", "45 mm").
heightAbovePlateNoThe commons' height above the plate (HAP); left out, the seat bears on the whole plate.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioural context beyond that: both measurement systems are returned, templates are full-size in SVG and DXF, and the tool deliberately does not perform structural sizing.

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 front-loaded with the core action and then packs the output set into one dense sentence followed by a short scope limitation. It is efficient and mostly earns its length, though the long enumeration of outputs makes it somewhat heavy to scan.

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 complex 25-parameter layout tool with an output schema, the description covers the essential purpose, outputs, and boundary condition. It does not explain input relationships such as pitch versus pitchDegrees, but those are handled by the rich schema and output schema.

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 100%, so every parameter is already documented in the input schema. The description reinforces that dimensions and stock come from the caller and that both systems are returned, but it does not add syntax or format guidance beyond what the schema provides.

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?

The description states a specific verb and resource: 'Lays out a gable or hip roof (optionally a gable wing with valleys).' It then enumerates the concrete outputs, including rafter lengths, birdsmouth/HAP, saw settings, hip backing, cut list, and templates. This clearly distinguishes it from generic calculation or cut-optimisation siblings.

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 a clear context: layout of roof framing from the caller's own dimensions, with an explicit scope exclusion that it is 'Geometry only: it does not size structure.' It does not name alternative tools for structural sizing, so it stops short of full routing guidance.

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