Skip to main content
Glama
millwork-mcp-lite

millwork-mcp-lite

Review cabinet schedule

review_cabinet_schedule
Read-onlyIdempotent

Check a cabinet schedule for duplicate tags, invalid types, sizes, and configuration issues before parts are calculated or cut; errors block the cut list and warnings need confirmation.

Instructions

Check a cabinet schedule for mistakes before anything is calculated or cut.

Use this first on any schedule read from drawings or typed by a person. It does not build parts; use build_cutlist for that (build_cutlist also runs this review and refuses to continue on errors).

Checks: duplicate tags, unknown cabinet types, non-positive sizes, widths outside 9-48", single doors wider than 24", drawer bases with no drawers, shelves in sink bases, unusual base heights (not 30-36") and deep wall cabinets (over 16").

Returns: {job_number, ok (true when there are no errors), errors (count), warnings (count), issues: [{level: "error"|"warning", cabinet: tag, message}]}. Errors block the cut list; warnings need a person to confirm.

Example: {"job": {"job_number": "K-101", "cabinets": [{"tag": "B1", "type": "base", "width": 36, "height": 34.5, "depth": 24, "doors": 1}]}} -> ok=true with one warning that the single door would be about 36" wide.

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

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.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description goes well beyond them by enumerating every check performed, stating that errors block the cut list while warnings require human confirmation, and describing the exact issue payload. This tells the agent how to interpret the result, not just that the call is safe.

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 purpose, then the sibling boundary, then the check list, then the return contract, then an example. The check enumeration is long but each item is a concrete rule the agent could otherwise only learn by trial, so no sentence is wasted.

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, and the description compensates by specifying the return shape and the semantics of 'ok', 'errors', 'warnings' and 'issues'. Combined with the checks list and example, an agent has everything needed to call it and interpret the result.

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% and the single 'job' parameter is fully documented in the schema, so baseline would be 3. The description adds a worked end-to-end example payload and clarifies the error/warning split of the return, which gives marginal extra meaning but does not explain the nested cabinet fields beyond what the schema already does.

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 ('Check a cabinet schedule for mistakes') and immediately delimits scope against the sibling: 'It does not build parts; use build_cutlist for that.' An agent can distinguish this from build_cutlist without opening either 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?

Gives explicit when-to-use ('Use this first on any schedule read from drawings or typed by a person'), names the alternative (build_cutlist) and its relationship ('build_cutlist also runs this review and refuses to continue on errors'), which also explains why one might skip this call.

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