Skip to main content
Glama
millwork-mcp-lite

millwork-mcp-lite

Calculate edgebanding

calculate_edgeband
Read-onlyIdempotent

Calculate the linear feet of edgebanding a cabinet job requires, grouped by material code and including a waste allowance for trimming and setup.

Instructions

Calculate the linear feet of edgebanding a job needs, per material, with a waste allowance.

Use when ordering edgeband rolls or pricing edgebanding. For sheet goods use count_sheets; for the individual parts and which edges they get, use build_cutlist (its edgeband field drives this total).

Counted edges: the front edge of sides, bottoms, tops, top rails and adjustable shelves ('front'), and all four edges of doors and drawer fronts ('all'). Backs get no edgebanding. Edgeband is grouped by the part's material code, so doors in front_material are totalled separately from case parts.

Parameters: waste_pct is the extra percentage added for trimming and machine setup, 0-50 (default 10).

Behaviour: read-only and deterministic. Runs review_cabinet_schedule first and returns {error, review} instead of totals if the schedule has errors.

Returns: {job_number, waste_pct, by_material: {code: {linear_feet, with_waste_linear_feet}}, total_with_waste_linear_feet}. Feet are rounded to 0.1.

Example: one 30" x 30" x 12" wall cabinet with one door and waste_pct=0 gives 19.7 linear feet of the case material (sides, bottom and top front edges plus the door perimeter).

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

Input Schema

NameRequiredDescriptionDefault
jobYesThe cabinet job: job_number, material codes and the cabinets list (inches).
waste_pctNoWaste allowance in percent. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds substantial behavior beyond them: which edges are counted per part type, that backs get none, material-code grouping, and that review_cabinet_schedule runs first and short-circuits with {error, review}. It even discloses rounding to 0.1 ft — only the example's role as a sanity check is left implicit.

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?

Front-loaded with purpose and routing, then labeled sections (Counted edges, Parameters, Behaviour, Returns, Example) that make it skimmable. It is long for a two-parameter tool and the worked example, while useful for verification, is the one block an agent could arguably skip.

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?

With no output schema, the description supplies the full return shape, the error path and its guard tool, the rounding convention, and the edge-counting rules that determine the totals. An agent has everything needed to call it and interpret the result correctly.

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%, so both parameters are already documented, and the description's waste_pct note (range, default) largely restates the schema. It does add real meaning to the material fields by explaining that doors use front_material and are totalled separately from case parts, but that is a modest increment over a fully described schema.

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 and resource — linear feet of edgebanding per material with waste allowance — and immediately scopes it against siblings count_sheets and build_cutlist. An agent can distinguish it from build_cutlist purely from this text.

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?

Gives explicit when-to-use cases (ordering rolls, pricing) and names the alternatives with the condition that selects each: sheet goods → count_sheets, per-part edge assignment → build_cutlist. Nothing is left to inference.

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