Skip to main content
Glama
millwork-mcp-lite

millwork-mcp-lite

Count sheets

count_sheets
Read-onlyIdempotent

Calculates total sheets per material needed for a cabinet job, giving bid and ordering totals without cut layouts. Returns sheet counts, yield percentages, and oversize-part warnings.

Instructions

Count how many full sheets each material in the job needs (quick material takeoff).

Use for bids and ordering ("how many sheets of melamine do I need?"). It runs the same panel-saw nesting as nest_sheets for every material but returns only the totals; call nest_sheets when someone needs the layouts.

Returns: {job_number, sheet_size, materials: {code: {sheets, yield_pct, oversize_parts}}}. oversize_parts counts parts that do not fit the sheet and need a bigger sheet or a joint.

Example: the bundled sample kitchen (8 cabinets) returns 9 sheets of 3/4" case material and 3 sheets of 1/4" back on 48 x 96 sheets.

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

Input Schema

NameRequiredDescriptionDefault
jobYesThe cabinet job: job_number, material codes and the cabinets list (inches).
sheet_widthNoSheet width in inches. Default 48.
sheet_lengthNoSheet length in inches. Default 96.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior beyond them: it runs the same panel-saw nesting as nest_sheets for every material, returns only totals, and explains that oversize_parts counts parts needing a bigger sheet or joint. The bundled-sample example gives a concrete sense of output magnitude.

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?

Front-loaded with the purpose and the sibling routing in the first two sentences, then returns and an example. Every sentence carries information; the example is illustrative rather than filler.

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 return-value burden and does so explicitly, naming each returned field and the meaning of the non-obvious one (oversize_parts). Combined with 100% schema coverage on inputs, an agent has everything needed to call and interpret this tool.

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 (job, sheet_width, sheet_length, and the nested cabinet fields) is already documented in the schema. The description adds little parameter-level guidance beyond implying default 48x96 sheets via the example; baseline 3 applies when the schema does the heavy lifting.

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: count how many full sheets each material in a job needs, plus a parenthetical gloss ('quick material takeoff'). It also explicitly contrasts with the sibling nest_sheets, which returns layouts rather than totals.

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 concrete use cases ('bids and ordering', with a sample question) and names the alternative tool plus the condition that selects it: 'call nest_sheets when someone needs the layouts.' Both when-to-use and when-not-to-use are present.

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