Skip to main content
Glama
rdolan5

solidworks-mcp

by rdolan5

solidworks_sketch

Destructive

Create and edit SOLIDWORKS sketches by adding entities, dimensions, and relations, then applying fillet, chamfer, offset, mirror, or convert operations before exiting.

Instructions

solidworks_sketch: dispatches on payload.operation to one of the capability-module handlers for [add_dimension, add_entities, add_relation, begin, chamfer, convert_entities, exit, fillet, mirror, offset]. Each operation has its own typed field set (see the tool's input schema); unspecified fields fall back to the module function's own default. Lengths/angles follow each field's documented unit convention (SI unless the function accepts a unit field).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYes
documentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

The description does not mention side effects, destructive behavior, or safety considerations, relying solely on annotations (destructiveHint: true). It does not explain the behavioral implications of the operations, such as sketch modification or rebuild.

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?

The description is a single, focused sentence that conveys the essential dispatch mechanism and parameter conventions without unnecessary verbosity. It is concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks information about return values, output format, or examples of usage. It also does not clarify the relationship to sibling tools, making it difficult for an agent to fully understand the context and integration points.

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?

The description provides general parameter semantics: specifies that unspecified fields fall back to defaults and that lengths/angles follow unit conventions (SI unless a `unit` field exists). However, it does not detail individual parameters, and the input schema lacks field descriptions, leaving many specifics ambiguous.

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 clearly states it is a dispatcher for sketch operations based on payload.operation, enumerating the supported operations. It identifies the resource (sketch) and the action (dispatch), but does not explicitly differentiate it from the sibling solidworks_sketch_begin tool, though the operation list incluses 'begin'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this dispatcher versus the specific sibling tools (e.g., solidworks_sketch_begin). The description does not mention alternatives or conditions for selecting this tool.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rdolan5/solidworks-mcp-2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server