Skip to main content
Glama

cut_out

Cut a hole in a floor area shape for columns, drains, or casework. Uses boolean subtraction to handle overlapping cuts without double-deducting and adds perimeter.

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). 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 hole's ring, image px, fully inside the parent
parent_shape_idYesA committed floor_area shape id (list_shapes)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
holesYesHoles the parent now carries
hole_sfYesWhat this cut actually removed from the parent's net — 0 when the ring fell entirely inside an existing hole
parent_netYes
deduct_shape_idYesThe reconciled deduct — carries cuts_shape_id; totals skip it (the parent nets the hole)
parent_shape_idYes
Behavior5/5

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

With no annotations provided, the description carries full burden. It thoroughly discloses behavior: boolean subtract semantics, set subtraction avoiding double-deduction, perimeter addition, journaling behavior (undo_last restores parent+hole together), refusal conditions (fully-inside, edge-crossing, erasure/splitting), coordinate system details, and how report/legend read the reconciled number. This is exceptional transparency.

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 long but every sentence delivers essential information—geometry semantics, refusal rules, journaling, coordinates, and tool alternatives. The logical flow (behavior → usage → refusals → journaling → coordinates) is coherent, though a structured list would improve scanability. It earns its length given the tool's complexity.

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?

For a complex boolean geometry tool with no annotations, the description covers all critical aspects: operation semantics, edge cases, failure modes, undo/delete behavior, coordinate handling, and integration with report/legend. It even addresses multi-cut composition and rebuild from snapshots. Nothing important is missing.

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?

Although schema coverage is 100%, the description adds meaning beyond the schema: verts are image px at render scale 2.0, fully inside parent, parent must be committed and from list_shapes, and coordinate origin is top-left y-down. It enriches both parameters with context that the schema alone does not provide.

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 uses a specific verb ('Cut') and resource ('committed floor_area shape'), clearly distinguishing it from sibling tools. It explicitly contrasts with measure_polygon role:deduct for independent deductions, making the tool's purpose unambiguous.

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?

Provides explicit guidance on when to use this tool (columns, floor drains, casework islands) and when not to (use measure_polygon role:deduct for non-hole deductions, edit_shape for boundary corrections, trace pieces as rooms instead of splitting). This is exactly the kind of alternative/exclusion guidance the dimension asks for.

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

Install Server

Other Tools

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