Skip to main content
Glama

cut_out

Cut a hole in a floor area shape or clip a wall run by drawing a ring; subtracts the region and reconciles overlaps so quantities stay accurate.

Instructions

Cut a REAL hole in a committed floor_area shape (#206) — the way the canvas cuts one (#137): the same lib/cutout.js boolean subtract, so the two surfaces can never disagree about what a hole holds. The parent keeps its outer ring plus the reconciled hole(s) (verts_norm_holes), its computed nets for real — N cuts compose, overlap between cuts never double-deducts (set subtraction), a hole ADDS perimeter — and the deduct commits carrying cuts_shape_id so the report and legend read the reconciled number, never a second arithmetic pass. This is the verb for a column, a floor drain, an island of casework INSIDE a room; an independent measure_polygon role:"deduct" stays the tool for a deduction that isn't a hole in one parent. Refusal over guessing: the ring must sit FULLY inside the parent's outer ring (an edge-crossing cut is a boundary correction — edit_shape the parent instead), and a cut that would erase the parent or split it in two refuses whole (trace the pieces as rooms). One journal entry — undo_last restores parent and hole together; delete_shape on the deduct later reverts the cut too (a multi-cut parent rebuilds from the chain's pristine snapshot minus the survivors). AN OPEN RUN IS CLIPPED, NOT SUBTRACTED: wall tile (surface_area) and base/transitions (linear) are polylines traced in plan, so the ring removes the stretch it covers, the run keeps its id and takes what survives, and a cut through the MIDDLE leaves the far side as its own shape (same condition, same height) — quantities ride the surviving length, which is exact, since wall SF is LF × height and a border's SF is LF × thickness. No deduct is minted for a run: there is no area for one to sit on, and a deduct's SF counts against the FLOOR total a run never fills. A ring that misses the run, one that swallows it whole (delete_shape it), and a curved run (its verts are control points) all refuse. Coordinates are image px at render scale 2.0: PDF pt × 2, origin top-left, y down (the browser canvas's native space). Sheet payloads carry dims in both px and pt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vertsYesThe ring, image px — fully inside the parent for an area; over the stretch to remove for a run
parent_shape_idYesA committed floor_area shape id, or an open run (surface_area / linear) to clip (list_shapes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
holesNoArea parent: holes the parent now carries
piecesNoRun parent: every stretch that survived the cut — more than one when the ring fell in the middle
hole_sfNoArea parent: what this cut actually removed from the parent's net — 0 when the ring fell entirely inside an existing hole
shape_idNoRun parent: the run that was clipped — it keeps its id and takes the first surviving stretch
parent_netNo
removed_lfNoRun parent: length the cut took out
removed_sfNoRun parent: the SF that rode on that length
measure_roleNoRun parent: surface_area or linear
deduct_shape_idNoArea parent: the reconciled deduct — carries cuts_shape_id; totals skip it (the parent nets the hole)
parent_shape_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv0.1.19
    • changedInput schema / properties / parent_shape_id / description
      Previous value: -"A committed floor_area shape id (list_shapes)"New value: +"A committed floor_area shape id, or an open run (surface_area / linear) to clip (list_shapes)"
    • changedInput schema / properties / verts / description
      Previous value: -"The hole's ring, image px, fully inside the parent"New value: +"The ring, image px — fully inside the parent for an area; over the stretch to remove for a run"
    • changedOutput schema / properties / deduct_shape_id / description
      Previous value: -"The reconciled deduct — carries cuts_shape_id; totals skip it (the parent nets the hole)"New value: +"Area parent: the reconciled deduct — carries cuts_shape_id; totals skip it (the parent nets the hole)"
    • changedOutput schema / properties / hole_sf / description
      Previous value: -"What this cut actually removed from the parent's net — 0 when the ring fell entirely inside an existing hole"New value: +"Area parent: what this cut actually removed from the parent's net — 0 when the ring fell entirely inside an existing hole"
    • changedOutput schema / properties / holes / description
      Previous value: -"Holes the parent now carries"New value: +"Area parent: holes the parent now carries"
    • addedOutput schema / properties / measure_role
      Added value: +{
      +  "description": "Run parent: surface_area or linear",
      +  "type": "string"
      +}
    • addedOutput schema / properties / pieces
      Added value: +{
      +  "description": "Run parent: every stretch that survived the cut — more than one when the ring fell in the middle",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "lf": {
      +        "description": "This piece's own length",
      +        "type": "number"
      +      },
      +      "sf": {
      +        "description": "LF × the height (wall) or the thickness (border) it was measured at",
      +        "type": "number"
      +      },
      +      "shape_id": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "shape_id",
      +      "lf",
      +      "sf"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / removed_lf
      Added value: +{
      +  "description": "Run parent: length the cut took out",
      +  "type": "number"
      +}
    • addedOutput schema / properties / removed_sf
      Added value: +{
      +  "description": "Run parent: the SF that rode on that length",
      +  "type": "number"
      +}
    • addedOutput schema / properties / shape_id
      Added value: +{
      +  "description": "Run parent: the run that was clipped — it keeps its id and takes the first surviving stretch",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "deduct_shape_id",
      -  "parent_shape_id",
      -  "hole_sf",
      -  "parent_net",
      -  "holes",
      -  "note"
      -]New value: +[
      +  "note"
      +]
  2. Addedv0.1.15

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it delivers richly: it explains the boolean-subtract mechanism, composition of cuts, set subtraction preventing double-deduct, perimeter additions, journaling behavior (undo_last restores parent and hole together), and the reversal via delete_shape. It also discloses coordinate conventions and run-clipping behavior, giving an agent deep insight into the tool's side effects and constraints.

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 quite long, but every sentence carries technical nuance essential for correct invocation, such as composition rules, journaling, and refusal conditions. It is front-loaded with the core purpose, though the parenthetical references (#206, #137) and some repetition about runs could be trimmed without losing meaning. Minor over-verbosity prevents a 5.

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?

Given the tool's complexity, no annotations, and an existing output schema, the description is remarkably complete. It covers all invocation parameters, coordinate systems, behavioral rules, edge cases, and refusal conditions, so an agent can correctly determine when and how to call it without needing external information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema covers both parameters, the description adds substantial meaning: verts are specified as image px at render scale 2.0 with origin top-left, y down, and parent_shape_id can be either a committed floor_area or an open run. It also explains how the ring interacts with runs (clipped, not subtracted) and lists refusal scenarios, going well beyond the schema's short descriptions.

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 verb and resource: 'Cut a REAL hole in a committed floor_area shape' and explicitly contrasts with measure_polygon's 'deduct' role for deductions that are not holes in a parent. It also distinguishes from edit_shape for edge-crossing boundary corrections. This makes the tool's purpose unambiguous and separates it from siblings.

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?

The description explicitly states when to use this tool: for a column, floor drain, or island of casework inside a room; and when to use alternatives: measure_polygon role 'deduct' for independent deductions, edit_shape for boundary corrections, and delete_shape for cuts that swallow a run whole. It also covers the clipped-run case and refusal conditions, providing clear routing guidance.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kentucky-ai/opentakeoff'

If you have feedback or need assistance with the MCP directory API, please join our Discord server