NestingCalc Calculators

flooring_calculator

Laminate/vinyl plank takeoff: planks, boxes and cost with offcut reuse between rows (best-fit), expansion gap, layout waste presets and direction.

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": {
      "room_width_m": "<room_width_m>",
      "room_length_m": "<room_length_m>",
      "plank_width_mm": "<plank_width_mm>",
      "plank_length_mm": "<plank_length_mm>"
    },
    "name": "flooring_calculator"
  }
}

Input Schema

Name	Required	Description	Default
`layout`	No		staggered
`direction`	No	Plank direction	length
`expansion_mm`	No
`price_per_m2`	No
`room_width_m`	Yes
`min_offcut_mm`	No	Offcuts shorter than this are not reused
`price_per_box`	No
`room_length_m`	Yes
`waste_percent`	No	Overrides the layout default
`plank_width_mm`	Yes
`planks_per_box`	No
`plank_length_mm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden of explaining behavior. It discloses that the calculation includes 'offcut reuse between rows (best-fit)', expansion gap, layout waste presets, and direction, which are meaningful algorithmic behaviors beyond the bare schema.

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?

One dense sentence with zero filler. The domain is front-loaded, followed by outputs and the key behavioral features, making it easy to scan while retaining high information density.

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

Completeness4/5

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

For a 12-parameter calculator with no output schema and no annotations, the description conveys the essential return values (planks, boxes, cost) and core modeling choices. It is compact but sufficient for an agent to select the tool; minor gaps remain around exact output structure and cost input priority.

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 only 25%, and the description helps by grouping features (planks, boxes, cost, offcut reuse, expansion gap, direction) that map to otherwise undocumented parameters. However, it does not clarify ambiguous relationships such as price_per_m2 versus price_per_box or how waste_percent interacts with layout presets, so it only partially compensates.

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 domain and resource ('Laminate/vinyl plank takeoff') and enumerates concrete outputs ('planks, boxes and cost') plus distinctive features such as offcut reuse, expansion gap, waste presetsees. This clearly separates it from siblings like tile_calculator or linear_cutting_optimizer.

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

Usage Guidelines4/5

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

The phrase 'Laminate/vinyl plank takeoff' establishes a clear context for when the tool applies, and the offcut/layout focus distinguishes it from general material calculators. It does not explicitly name alternatives or hard exclusions, so it earns a 4 rather than 5.

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

All NestingCalc Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?