Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Check Drawing Completeness

check_drawing
Read-onlyIdempotent

Validates an active SolidWorks drawing for completeness before export by checking views, dimensions, title block fields, dangling annotations, and BOM presence.

Instructions

Check the active drawing is complete before exporting it: views, dimensions, title block, BOM.

Read-only. Findings: view_off_sheet (error), view_not_dimensioned (warning; isometric and detail views excepted), title_block_field_empty (warning: title, drawn by, revision), dangling_annotation (error) and bom_missing (warning, an assembly with no BOM). Each names the tool that fixes it. It checks completeness, not a drafting standard. Needs: an open, active drawing. Returns: passed (no errors), errors, warnings, findings (each rule, severity, message, maybe view), views and report (the facts read).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already cover readOnly/idempotent/non-destructive, yet the description still adds substantive behavior: the exact rule set, the severity assigned to each rule, and the exception for isometric and detail views under view_not_dimensioned. It also notes that findings name the tool that fixes them, which is actionable context unavailable in structured fields.

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 the purpose, then organized into rules, scope limit, precondition, and return shape. The rule list is dense but each clause carries distinct information; the returns sentence partially duplicates the output schema, costing a little tightness.

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 zero-parameter check tool, an agent knows the trigger, the precondition, all possible findings with severities, and the shape of the result. Nothing needed to invoke it correctly or interpret results 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?

Zero parameters establishes a baseline of 4. The description correctly clarifies that the tool takes no target argument and instead operates on the active drawing, which is the only 'input' semantics an agent needs.

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 ('check the active drawing is complete') and enumerates the four checked areas (views, dimensions, title block, BOM), which distinguishes it from the sibling check_* tools that target interference or sketch state.

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?

Gives a concrete trigger ('before exporting it'), a precondition ('needs an open, active drawing'), and an explicit scope boundary ('it checks completeness, not a drafting standard'). It does not name sibling checks to use instead when the concern is interference or sketch definition, so it falls short of a full when/when-not routing.

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