Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Hole Wizard Sizes

list_hole_sizes
Read-onlyIdempotent

List Hole Wizard hole types and sizes for a standard, or get dimensions for one size, from the installed SolidWorks library so you can choose valid inputs for hole creation.

Instructions

List the Hole Wizard's hole types and sizes for a standard, or one size's dimensions.

Read from SolidWorks' installed Hole Wizard library, so the sizes are the ones create_hole accepts; it works without SolidWorks running. Give hole_type for every hole type of that kind with its sizes, add fastener for one type only, or size for its dimensions (counterbore diameter and depth, head diameter, pitch: mm, inches for ansi_inch). Needs: SolidWorks' Toolbox library on this machine (or SOLIDWORKS_MCP_HOLE_LIBRARY). Changes: nothing. Returns: library with standard, hole_type, units and either hole_types (each name and sizes) or fastener and dimensions.

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": "list_hole_sizes"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesWhat to list. `hole_type` is required; `standard` is iso.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the data source (installed Hole Wizard library), the prerequisite (Toolbox library or SOLIDWORKS_MCP_HOLE_LIBRARY), the fact that it works without SolidWorks running, and 'Changes: nothing'. It also names the unit convention (mm, inches for ansi_inch).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the source, then the mode mapping, then prerequisites, effects, and return shape — each clause earns its place with no filler. Backtick-marked parameter names keep it scannable despite the density.

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?

Given nested parameters, an output schema, and a prerequisite dependency, the description covers source, side effects, units, and return structure so an agent can call it correctly. The return-shape sentence slightly duplicates the output schema, but it usefully ties the mode choice to which keys appear.

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 the baseline is 3, but the description adds real meaning: it explains that `size` resolves against the given hole type or 'the usual one', that `fastener` restricts to sizes only, and what dimension fields come back (counterbore diameter/depth, head diameter, pitch). That is semantics the schema descriptions do not fully carry.

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 concrete verb and resource ('List the Hole Wizard's hole types and sizes') and scopes the two modes (whole standard vs. one size's dimensions). It also distinguishes itself from the write-side sibling by noting the sizes are exactly the ones `create_hole` accepts.

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?

Explicitly maps inputs to behaviors: `hole_type` alone enumerates every type with sizes, adding `fastener` narrows to one type, adding `size` returns that size's dimensions. It does not spell out when to prefer this over siblings, but the create_hole reference gives the read-vs-write context implicitly.

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