Skip to main content
Glama
millwork-mcp-lite

millwork-mcp-lite

Nest sheets for a panel saw

nest_sheets
Read-onlyIdempotent

Lays out one material's parts on full sheets for a panel saw and reports the strip-cut, guillotine-safe cutting plan, sheet count, and yield.

Instructions

Lay out one material's parts on full sheets for a panel saw and report the cutting plan.

Use when someone needs the actual sheet layouts (which part goes where). For just the number of sheets across every material, count_sheets is faster. The layout is strip-cut and guillotine-safe: each sheet is ripped into strips across its width, then parts are crosscut from each strip. Parts keep their listed grain direction (length runs along the sheet). 1/4" is trimmed off each sheet edge. Not for CNC routers.

Parameters: material is a material code from the job (defaults to case_material); sheet_length and sheet_width in inches (default 96 x 48); kerf is the saw blade width in inches (default 0.125).

Returns: {job_number, material, sheet_size, sheets_needed, parts_nested, overall_yield_pct, oversize_parts: [parts too big for the sheet], sheets: [{sheet, yield_pct, strips: [{rip_width, y, parts: [{cabinet, name, length, width, x}]}]}]}. x and y are inches from the sheet's corner.

Example: {"job": {...}, "material": "MEL-WHT-34", "sheet_length": 97, "sheet_width": 49}.

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": "nest_sheets"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesThe cabinet job: job_number, material codes and the cabinets list (inches).
kerfNoSaw blade kerf in inches. Default 0.125 (1/8").
materialNoMaterial code to nest, e.g. "MEL-WHT-34". Empty = the job's case_material.
sheet_widthNoSheet width in inches, e.g. 48, 49, 60.
sheet_lengthNoSheet length in inches, e.g. 96, 97, 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the layout behavior in detail: strip-cut, guillotine-safe, grain direction is preserved, and 1/4 inch is trimmed from each sheet edge. It also describes what the return contains and flags oversize parts, which is useful behavioral context for a read-only layout tool.

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?

The description is front-loaded with purpose and usage guidance, then separates parameters, return value, and example into clear sections. Given that there is no output schema, the return explanation earns its place and is not excessive.

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?

For a tool with no output schema, the description provides the return structure, coordinate meaning, defaults, layout algorithm, and key restrictions. An agent has enough information to decide when to call it and how to interpret the results.

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 the schema already documents all five parameters thoroughly. The description adds some practical context, such as material defaulting to case_material and units in inches, but most of its parameter wording repeats schema information rather than adding new semantics.

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: lay out one material's parts on full sheets for a panel saw and report the cutting plan. It clearly distinguishes the tool from count_sheets by explaining that this produces actual sheet layouts rather than just sheet counts.

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 gives explicit when-to-use guidance: use when someone needs actual sheet layouts. It also names the alternative (count_sheets is faster for just counts) and states an exclusion: not for CNC routers.

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