Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Centre Marks

auto_center_marks

Adds centre marks to holes, slots, and optional fillets in a selected SolidWorks drawing view, preparing the view for hole dimensioning.

Instructions

Insert centre marks on the holes, slots and (optionally) fillets of one drawing view.

Use it after placing views, before dimensioning holes. Adding none is still a success: the view may have no unmarked circular edges. Needs: an open drawing with the named view (see list_drawing_views). Changes: adds centre-mark annotations to the view. Returns: data with center_marks_added and the counts before and after.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe view. `view_name` is required; `mark_holes` and `mark_slots` default to on, `mark_fillets` to off.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false; the description adds real value on top by stating the change made ('adds centre-mark annotations to the view') and normalizing the no-op case ('Adding none is still a success'). One residual gap: with idempotentHint=false, it does not say whether re-running duplicates existing marks.

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?

Short, front-loaded, and organized with explicit 'Needs:', 'Changes:' and 'Returns:' labels so an agent can scan constraint, side effect and output separately. No sentence is filler.

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 nested-parameter mutation tool with an output schema and annotations, this covers purpose, prerequisite, side effect and no-op semantics. The return shape is mentioned by name of fields, which is sufficient since an output schema exists.

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

Parameters3/5

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

Schema coverage is 100% and the nested input_data object already documents view_name, the hole/slot defaults and the fillet default. The description only restates which categories are optional ('optionally fillets'), adding little meaning beyond what the schema provides, so the baseline 3 applies.

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?

Specific verb and resource: 'Insert centre marks on the holes, slots and (optionally) fillets of one drawing view' — it names exactly the geometry targeted and scopes the operation to a single view. It also implicitly separates itself from the dimensioning siblings by stating the ordering relative to dimensioning.

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?

'Use it after placing views, before dimensioning holes' gives explicit sequencing, and 'Needs: an open drawing with the named view (see list_drawing_views)' gives the prerequisite and points at the sibling that supplies it. It lacks an explicit when-not / alternative branch (e.g. when to prefer manual add_annotation), which keeps it just short of a 5.

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