Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

hole_wizard

Creates ISO holes at points on flat faces—simple, counterbore, countersink, or tapped—with optional depth and edge- or origin-based dimensions; multiple points can form one feature.

Instructions

Make a standard ISO Hole Wizard hole at a model point on a flat face. hole_type: 'simple' (drilled; size = standard ISO drill diameter in mm; with a unit other than mm write it '6.5mm'), 'counterbore' (socket head cap screw; size like 'M6'), 'countersink' (countersunk socket screw; size like 'M6') or 'tapped' (size like 'M6'; with depth, depth is the tap drill depth and the thread is 1 x the thread diameter deep). Leave depth out for a through hole. Several holes of the same type and size on one flat face: give points instead of x, y, z; they become one Hole Wizard feature (one call, one feature). The positions are dimensioned from the edges named in dimension_from (the user's references; one call per group of holes sharing their edges); what no named edge covers is dimensioned from the origin and listed in dimensions_from_origin (not from your spec); an edge dimension that could not be made is listed in edge_dimensions_missing with a warning.

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": {
      "size": "<size>"
    },
    "name": "hole_wizard"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoX of the hole position on the face
yNoY of the hole position on the face
zNoZ of the hole position on the face
sizeYesDrill diameter in mm for 'simple' (e.g. '6.5'), or thread size for the others (e.g. 'M6')
unitNoUnit for x, y, z and depth (mm, cm, m, inch or ft)
depthNoHole depth; omit for a through hole
pointsNoSeveral hole positions on the same flat face, e.g. [{"x": 20, "y": 6, "z": 15}, {"x": 70, "y": 6, "z": 15}]; replaces x, y, z
hole_typeNoKind of holesimple
dimension_fromNoThe edges the user measures the holes from, each by a point on it (model coordinates), e.g. [{"x": 0, "y": 6, "z": 0}] for "20 mm from the outside face"; one or two (one per direction). Without it, the positions are dimensioned from the origin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 full burden and does a fair amount: it discloses that multiple points collapse into a single Hole Wizard feature, that positions become edge- or origin-dimensioned, and that unreachable edge dimensions surface in edge_dimensions_missing with a warning. That is meaningful side-effect and result-shape disclosure. Gaps remain on preconditions beyond 'flat face' (what happens on a non-flat or invalid face) and on permission/error behavior.

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 core action and the hole_type contract are front-loaded, and every clause carries operative information about size, depth, points, or dimension_from. It is a single dense run-on block, though, and the dimensioning/return-value discussion at the end could be broken out for faster scanning.

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 9-parameter modeling tool with no annotations and no output schema, the definition covers the essential contract: what gets created, how size and depth are interpreted per hole_type, how multi-hole placement works, and how dimension references are resolved or reported as missing. It is close to complete, lacking only edge-case behavior for non-flat faces and failure modes.

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 coverage is 100%, so baseline would be 3, but the description adds real meaning the schema does not: 'size' means a drill diameter for 'simple' but a thread size like 'M6' for the others, and when a non-mm unit is used the value must be written as '6.5mm'. It also explains that depth on a tapped hole is the tap drill depth with thread depth equal to one thread diameter, and that points supersedes x, y, z.

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 opens with a specific verb and resource: 'Make a standard ISO Hole Wizard hole at a model point on a flat face', and enumerates the four hole_type variants. An agent can tell immediately this creates a hole feature rather than a sketch, edge treatment, or pattern. It stops short of naming a sibling it is not, but the operation is unambiguous.

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?

It gives concrete conditional guidance for the main branch points: use 'points' instead of x/y/z when several same-type, same-size holes sit on one flat face (one call, one feature), and omit depth for a through hole. It also states that one call should cover a group of holes sharing the same edge references. It does not address when to prefer a different tool (e.g. pattern operations) for repeated hole layouts.

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

Deploy Server

Other Tools