Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_hole

Adds a through-hole of specified diameter to a plate at an X/Y offset from its center, then rebuilds the model for updated CAD geometry.

Instructions

在平板上加一个通孔(孔心相对板中心偏移 x/y)。模型会整体重建。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sw_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_mmNo
y_mmNo
diameter_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It does disclose one valuable trait: the model is fully rebuilt ('模型会整体重建'), signaling an expensive mutation. It says nothing about whether the hole is additive or replaces existing holes, whether the rebuild discards unsaved state, how errors are surfaced, or what the call returns.

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?

Two short sentences with the action and coordinate frame front-loaded, followed by the side effect. No filler words and nothing to trim; the parenthetical keeps the offset semantics attached to the action instead of in a separate clause.

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 three-parameter mutation tool with no annotations or output schema, the description covers the core action, the coordinate reference frame, and the rebuild side effect. It is still incomplete: diameter semantics and the default 8mm value are not mentioned, the rebuild's consequence for the existing model is not stated, and there is no indication of failure modes or whether the operation is additive.

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

Parameters1/5

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

Schema description coverage is 0% and none of the three parameters are explained. The description adds meaning only for x_mm and y_mm by defining their reference origin (offset from plate center). diameter_mm is never mentioned, and the units, the 8mm default diameter, and the 0mm default offsets appear only in the schema.

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 states a specific verb and resource in Chinese: add a through hole on the plate, with the hole center offset x/y from the plate center. This is far more informative than a tautology. It stops short of naming how it differs from the sibling sw_holes_clear, so the agent must infer the distinction (create one hole vs. clear holes).

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?

Usage is only implied: the agent can infer it should be used when a single through hole is needed on a flat plate. The description gives no explicit when-to-use, no prerequisites, and no mention of the relevant sibling sw_holes_clear or of ordering constraints.

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