Skip to main content
Glama
hjbaard

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_hole_on_face

Drill a round hole on any planar face at a 3D point, through-all or blind depth. Returns mass properties and dimensions.

Instructions

Drill a round hole on ANY planar face, centred at 3D point (x, y, z) mm.

face is "+x"/"-x"/"+y"/"-y"/"+z"/"-z": the face facing that way through the point is drilled, so a pocket floor or a step works too. Through all, or depth_mm deep (blind: heat-set inserts, screw pilots). Returns mass properties and dimensions (diameter, x, y, depth).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faceYes
nameNoHole
x_mmYes
y_mmYes
z_mmYes
depth_mmNo
diameter_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / depth_mm
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Depth Mm"
+}
  2. First observedv0.4.0

TDQS

A3.8/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 well: it defines through-all vs blind behaviour via depth_mm, explains the direction-string semantics, and states what is returned (mass properties and dimensions). It omits error/failure behaviour and permission needs, but the mutation semantics are well disclosed.

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?

Three dense, front-loaded sentences with no filler; the primary action leads and the face/depth details follow. Slightly compact given the number of concepts packed in, but every sentence earns its place.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the geometry semantics and even the return value. Minor gaps remain around name and diameter, but an agent could call this correctly from the description alone.

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 description coverage is 0%, so the description must compensate and largely does: it enumerates the face direction strings, ties x/y/z to a 3D centre point in mm, and explains depth_mm as null-for-through vs a blind depth. It does not clarify diameter_mm or the name default, but the geometry-critical parameters are covered.

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?

States a specific verb (drill) and resource (round hole) with a clear scope: on ANY planar face, centred at a 3D point. It does not explicitly differentiate itself from sibling tools add_hole, add_hole_wizard, or add_counterbore_hole, so an agent must infer 'on_face' means anchored to an arbitrary planar face.

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?

Gives real usage context: pocket floors and steps work too, and blind holes suit heat-set inserts and screw pilots. However, it never says when to pick this over add_hole / add_hole_wizard, so alternative selection is left to inference.

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