Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Hole Wizard Hole

create_hole

Adds standard Hole Wizard holes—simple, counterbored, countersunk, or tapped—at points on a flat face, sizing them from the library instead of sketching and cutting circles.

Instructions

Add a standard Hole Wizard hole (simple, counterbored, countersunk or tapped) at a point on a flat face.

Use it instead of sketching a circle and cutting: the hole is sized from the standard, so it fits the fastener and a drawing shows its callout. Several holes on one face: give the rest as positions (one feature, a hole at each point); a regular grid can also use pattern_linear. Sizes come from the Hole Wizard library (list_hole_sizes): an unknown size is refused, with the nearest ones, before anything is made. A simple hole can't be through all in SolidWorks, so it is made blind through the part (end_condition_used, with a warning). It fails when the volume doesn't change. Needs: an open part with a flat face at face_point. Changes: adds a hole feature. Returns: hole with name, hole_count, hole_type, standard, fastener (the hole type used), size, end_condition, end_condition_used, and volume_before, volume_after and volume_change (mm³).

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": {
      "input_data": "<input_data>"
    },
    "name": "create_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe hole. `face_point`, `hole_type` and `size` are required; `standard` is iso and `end_condition` through_all (blind needs `depth`).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), it discloses prerequisites (open part with a flat face), validation behavior (unknown size refused with nearest matches before anything is made), a documented deviation (simple holes cannot be through-all, so they are made blind with a warning and `end_condition_used`), and a failure condition (no volume change). That is far more than the annotations convey.

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?

Front-loaded with purpose and alternative, then behavior, then effects and returns, so structure is sound. It is dense in places, and the closing enumeration of every returned field largely duplicates the existing output schema, which is the one stretch that does not fully earn its space.

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 mutation tool with nested parameters and an output schema, the description covers prerequisites, validation, side effects, failure mode, and the simple-hole caveat, all of which are the parts the schema cannot express. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3; the description adds real meaning by tying `size` to the Hole Wizard library and explaining that `positions` creates one feature with a hole at each point rather than separate features. It adds somewhat less for `depth`, `standard`, or `fastener`, which the schema already documents well.

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?

States a specific verb and resource ('Add a standard Hole Wizard hole') and enumerates the four hole types plus the geometric constraint ('at a point on a flat face'). It also contrasts with the naive approach (sketch a circle and cut), so an agent can tell exactly what this tool produces versus building the geometry manually.

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?

Explicitly says to use it instead of sketching a circle and cutting, and routes multi-hole cases: extra points go in `positions` as one feature, while a regular grid may use `pattern_linear`. It also names `list_hole_sizes` as the prerequisite lookup, which is exactly the sibling routing an agent needs.

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