Craft Quantities: construction material calculators

Worktop run round corners: pieces, joints and lengths

fit_worktop_run

Read-onlyIdempotent

A worktop along several wall faces, as the Construction Canvas cuts it: each piece's true shape at the room's real angles, butt or mitre joints at corners, long straights joined, the front run and free ends, and the blanks nested on worktop lengths with the cut order and banding. Not sized.

Input Schema

Name	Required	Description	Default
`bow`	No	The back wall's greatest departure from straight. Left out, none.
`gap`	No	Left clear at each wall end. Left out, the kind's usual.
`kerf`	No	The saw's kerf. Left out, 3 mm (1/8 in).
`depth`	No	The finished depth, front edge to back wall. Left out, the kind's usual.
`faces`	Yes	The wall faces the run follows, in order, each with its length along the wall.
`grain`	No	Hold the grain or decor along the run (the default).
`start`	No
`stock`	No	An index into the kind's stock sizes for the market (listed in the answer's stockOffered). Left out, the size that buys least.
`detail`	No	full (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.	full
`finish`	No
`scribe`	No	Left on every edge that meets a wall, to scribe off in place. Left out, the kind's usual.
`system`	No	The unit system inputs left out open in, and the one the page link opens in. The answer comes in both.	metric
`corners`	No	Between face i and face i + 1 (one fewer than the faces): inside or outside, the room's inside angle, and how the pieces meet.
`jointAt`	No	Where a straight longer than the stock is joined, along its back from its start. Left out, an even split.
`bandFront`	No	Band the front edge of the fitted piece.
`inputUnits`	No	Send "base" to pass bare numbers on dimensioned inputs in base units (m, m², L, kg …), as the published test vectors are written. Without it a length, area or volume must carry its unit.
`bandAllowance`	No	Tape added to every banded edge for trimming flush.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world computation, so the description is not burdened with safety disclosure. The description adds some behavioral context by stating that the tool models the Construction Canvas cut, handles joints and nesting, and is 'Not sized.' However, it does not clarify what 'Not sized' implies operationally or how defaults are applied across the many parameters.

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?

The description is a single dense sentence that front-loads the core purpose and lists the outputs efficiently. It has minimal waste, though the long sentence and ambiguous 'Not sized' tail slightly reduce clarity.

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

Completeness3/5

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

The tool has 17 parameters, nested objects, and an output schema, so the return values need not be explained. Still, the description is thin for such a complex tool: it does not explain how to structure faces/corners or clarify the meaning of 'Not sized' in relation to the inputs. It is adequate given the rich schema but not complete.

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 88%, so parameter semantics are largely handled by the schema. The description adds only high-level references to joints, banding, cut order, and the 'Not sized' constraint, without enriching the meaning of key parameters like faces, corners, start, finish, or stock. Baseline 3 is appropriate 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (a worktop run along several wall faces) and enumerates what the tool produces: true shapes, butt/mitre joints, joined straights, front run, free ends, nested blanks with cut order and banding. It is clearly more than a restatement of the name. It does not, however, differentiate the tool from plausible siblings such as plan_room_trim, miter_chart, or fit_panel.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'Not sized' is the only usage-oriented hint, and it is ambiguous rather than a clear exclusion or prerequisite. An agent must infer the applicable scenario entirely from the name and description.

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

All Craft Quantities: construction material calculators tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?