Skip to main content
Glama
millwork-mcp-lite

millwork-mcp-lite

Build cut list

build_cutlist
Read-onlyIdempotent

Turns a cabinet schedule into a frameless cut list: part sizes, quantities, material square footage and edgebanding notes, with a schedule review before parts are returned.

Instructions

Turn a cabinet schedule into a part-by-part cut list for frameless cabinets.

Use when someone needs the parts to cut, a parts count, or square footage per material. For sheet counts use count_sheets; for sheet layouts use nest_sheets; for edgebanding length use calculate_edgeband.

Construction (generic defaults): full-height sides; bottom between the sides; two 4" top rails on base, drawer_base and sink_base, a full top on wall and tall; adjustable shelves 1/16" narrower than the opening and 1" plus the back thickness shallower than the box; an applied back, full width x full height; full-overlay doors and drawer fronts with a 1/16" reveal. Runs review_cabinet_schedule first and returns {error, review} instead of parts if the schedule has errors.

Returns: {job_number, summary: {total_pieces, by_material: {code: {pieces, square_feet}}}, parts: [{cabinet, name, material, length, width, qty, edgeband ("front"|"all"|""), notes}], review}. length is the long/grain direction; all sizes are finished inches.

Example: a 24" base with 1 door and 1 shelf gives 2 sides 34.5x24, a bottom 22.5x24, 2 top rails 22.5x4, a shelf 22.4375x22.75, a back 34.5x24 and a door 34.375x23.875.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job": "<job>"
    },
    "name": "build_cutlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe cabinet job: job_number, material codes and the cabinets list (inches).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered by structured data. The description does add real behavioral context beyond that: it runs review_cabinet_schedule first and returns {error, review} instead of parts when the schedule has errors. That is useful but is the main addition; the rest is construction rules and output layout rather than operational behavior such as sizing limits or performance.

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?

Purpose and routing come first, then construction defaults, then the return contract, then a worked example. It is long but every block is load-bearing, and the example converts abstract rules into concrete part dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full return contract: field-by-field shape including summary.by_material and the parts array with the edgeband enum, plus the error-path return. For a single nested-argument tool that derives many parts, nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3. The description goes further by explaining that all sizes are finished inches, that length is the long/grain direction, and by spelling out the construction conventions (full-height sides, bottom between sides, 4" top rails, 1/16" reveal) that give the nested job inputs their meaning.

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 opens with a specific verb and resource: 'Turn a cabinet schedule into a part-by-part cut list for frameless cabinets.' It names the output artifact and the domain, so an agent can distinguish it from count_sheets or nest_sheets without opening any schema.

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

Usage Guidelines5/5

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

It states the selection condition ('Use when someone needs the parts to cut, a parts count, or square footage per material') and then routes three sibling cases explicitly: count_sheets for sheet counts, nest_sheets for layouts, calculate_edgeband for edgebanding length. Both when-to-use and when-not-to-use are covered.

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