AnkusDrive

Overview Schema Source Related Servers Discussions Admin

Hole

hole

Drill parametric cutouts from sketch circles, with depth, threading, and head-clearance options. Handles through-body, blind, and countersink variants.

Instructions

Drill a parametric Hole from a sketch (one or more circles).

sketch: handle of a sketch placed on a face of an existing body feature. depth_type: 'Dimension' (use depth) or 'ThroughAll'. cut_type: 'None' | 'Counterbore' | 'Countersink' | 'Counterdrill'. When non-None, cut_diameter (head clearance) and cut_depth apply. threaded=True applies a tap. thread_type / thread_size are COUPLED enums — valid thread_size values DEPEND on thread_type ('M4' fits 'ISOMetricProfile' but not 'UNC'). Use list_thread_options() to discover thread_type values and list_thread_options(thread_type=...) for that type's valid sizes. intended_for ('print'|'machine'|'drawing'): drives ModelThread default when threaded=True so the caller doesn't have to know what ModelThread means. print → ModelThread=True. Required for 3D-printed threaded holes — the screw must engage the printed thread geometry; a smooth pilot won't tap itself. machine → ModelThread=False. CAM software reads thread metadata and drives a physical tap. Modeling thread bloats files and fights patterns/fillets. drawing → ModelThread=False. Drawings annotate threads symbolically. Explicit model_thread overrides intended_for. through ('wall'|'body'): preferred over depth_type/depth. 'wall' ray-casts to the first exit boundary and drills exactly one wall thick — critical on shelled bodies where 'body' (ThroughAll) would destroy the cavity. Implies direction='into_body'. Result carries wall_depth_mm. direction (preferred over reversed): 'into_body' picks the Reversed value that actually removes material; 'away_from_body' picks the value that removes none. Hole and Pocket interpret the raw flag differently. reversed: legacy raw flag, used only if neither through nor direction is set. strict: raise instead of warning on a degenerate hole (see below).

Returns {handle, name, volume, removed_volume, volume_ratio}, plus warnings ONLY when the hole consumed the whole body or removed nothing (the same two degenerate outcomes as boolean_op's cut). Warn-don't-fail is the default; pass strict=True in a scripted recipe to turn both into an error instead. direction='away_from_body' is an explicit request to remove nothing, so it never warns and never raises.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	No	Hole
`depth`	No
`sketch`	Yes
`strict`	No
`through`	No
`cut_type`	No	None
`diameter`	No
`reversed`	No
`threaded`	No
`cut_depth`	No
`direction`	No
`depth_type`	No	ThroughAll
`thread_size`	No
`thread_type`	No
`cut_diameter`	No
`intended_for`	No
`model_thread`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.5Sep 15, 2026

addedInput schema / properties / strict

Added value: +{
+  "default": false,
+  "title": "Strict",
+  "type": "boolean"
+}

First observedSep 13, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations are minimal (destructiveHint: false), so the description carries the full burden, and it excels. It discloses that direction='away_from_body' removes no material and that reversed is a legacy raw flag that differs between Hole and Pocket. It explains that 'through=wall' ray-casts to the first exit boundary and drills exactly one wall thick, critical behavior. It details the degenerate outcomes (consumed whole body or removed nothing) and the strict vs warn-don't-fail behavior, which is beyond annotations. No contradiction with annotations.

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 lengthy but well-structured with a header line and parameter definitions in a clear list format, making it easy to scan. It is front-loaded with the core purpose and then details each parameter in order. While it is very detailed, each sentence provides valuable information and earns its place—there is minimal filler. It is longer than ideal for conciseness but the structure compensates, so a 4 is appropriate.

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 tool with 17 parameters and no output schema, the description is exceptionally complete. It explains the return value structure (handle, name, volume, removed_volume, volume_ratio, plus warnings) despite no output schema, which is a quality addition. It covers parameters that are not self-evident from the schema (e.g., strict, through, direction, intended_for) and provides usage guidance that would prevent common errors. The description is a comprehensive manual for the tool.

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?

Schema description coverage is 0%, and the description compensates fully. It explains the meaning of depth_type ('Dimension' vs 'ThroughAll'), cut_type ('None' | 'Counterbore' | 'Countersink' | 'Counterdrill'), and how cut_diameter/cut_depth apply when non-None. It clarifies the coupled enums thread_type/thread_size and that valid values depend on each other (e.g., 'M4' fits 'ISOMetricProfile' but not 'UNC'). It interprets intended_for's values ('print' → ModelThread=True, 'machine'/'drawing' → False) and explains that 'through' and 'direction' override depth_type/depth/reversed.

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?

Clearly states it drills a parametric hole from a sketch (one or more circles), with an explicit verb ('Drill') and resource ('a parametric Hole from a sketch'). It distinguishes from siblings like 'pocket' (different operation) and 'boolean_op' (more general) by specifying 'parametric Hole' and the sketch-based input. The description goes beyond the title and schema to clarify that the sketch must be placed on a face of an existing body feature, which is a specific prerequisite.

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 extensive guidance on when to use specific parameters: through is 'preferred over depth_type/depth' and crucial for shelled bodies; direction is 'preferred over reversed'; intended_for is described with explicit use cases (print vs machine vs drawing) and alternatives (list_thread_options is named for discovering thread enums). It clearly states when to use 'through' versus 'depth_type' and when to use 'intended_for' versus manual thread settings. Exclusions are implied by naming alternatives like list_thread_options.

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

Deploy Server

Hole

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools