Skip to main content
Glama
solidworks-mcp

solidworks-mcp

hole

Drills round perpendicular features into a planar face at specified centers; supports metric screw clearances, tapped sizes, depths, counterbores, countersinks, and cosmetic threads.

Instructions

Drills round holes into a planar face, perpendicular to it.

centers: the hole centres [[x, y, z], ...] in mm, model coordinates, all on the SAME face (the face is found through the first one). size: metric screw size ("M3" ... "M24") with fit: close / normal / loose clearance hole (ISO 273) or tapped = tap drill diameter; or give diameter_mm. depth_mm or through_all=True. style: counterbore / countersink for socket head screws; with a metric size their dimensions are standard (ISO 4762 / ISO 10642, 90 degrees), otherwise give them. thread=True (with a metric size, fit="tapped", style="simple") adds a cosmetic thread to each hole (e.g. M6x1, shown in drawings and the thread callout), over thread_depth_mm or the whole hole.

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": {
      "centers": "<centers>"
    },
    "name": "hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNonormal
sizeNo
styleNosimple
threadNo
centersYes
depth_mmNoHole depth in mm (0 if through_all)
diameter_mmNoHole diameter in mm (0 if using metric size)
through_allNo
thread_depth_mmNoThread length in mm (0 = the whole hole)
counterbore_depth_mmNoCounterbore depth in mm
countersink_angle_degNoCountersink angle in degrees (0 < angle < 180)
counterbore_diameter_mmNoCounterbore diameter in mm
countersink_diameter_mmNoCountersink diameter in mm

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / thread
      Added value: +{
      +  "default": false,
      +  "title": "Thread",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / thread_depth_mm
      Added value: +{
      +  "default": 0,
      +  "description": "Thread length in mm (0 = the whole hole)",
      +  "minimum": 0,
      +  "title": "Thread Depth Mm",
      +  "type": "number"
      +}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent operation, so the description only needs to add behavioral context. It adds important constraints like the planar face requirement, same-face centers, ISO standard dimensions, and cosmetic thread behavior, but it does not mention active document requirements, feature-tree effects, or failure 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 first sentence states the core action, and the following labeled lines efficiently explain the most important parameters. The description is appropriately sized for a 13-parameter feature creation tool, with little wasted wording.

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

Completeness3/5

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

For a complex 13-parameter feature tool with an output schema and sparse annotations, the description covers the main geometry and sizing behavior well. It still leaves operational gaps around active document requirements, error conditions, and how the counterbore/countersink dimension parameters should be supplied when non-standard.

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

Parameters4/5

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

With 54% schema coverage, the description compensates by explaining key domain semantics: centers are in model mm on the same face, size accepts M3-M24 with fit meanings including tapped tap-drill diameter, depth can be explicit or through_all, and style supports standard counterbore/countersink dimensions. It adds meaning beyond the schema, though it does not explicitly map the counterbore/countersink depth, diameter, and angle parameters.

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 gives a specific verb and resource: it drills round holes into a planar face, perpendicular to that face. That is much clearer than the bare name, though it does not explicitly contrast itself with generic siblings such as cut_extrude or extrude.

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

Usage Guidelines3/5

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

It gives useful invocation conditions such as all centers being on the same face, choosing a metric size with a fit, and using depth_mm or through_all. However, it does not state when to prefer this tool over alternatives like cut_extrude, or when not to use it.

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