Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Add Sketch Chamfer

add_sketch_chamfer

Bevels corners of an open 2D sketch by selecting corner points, trimming adjoining entities and creating chamfer lines. Use it for sketch-profile chamfers; use add_chamfer for solid edges.

Instructions

Bevel corners of the open sketch, picking each corner by its point.

Use it for bevelled corners of a 2D profile; bevel a solid's edges with add_chamfer instead, last in the feature tree. distance alone cuts the same distance along both sides; add distance2 for a different second side, or angle (degrees) for a distance and an angle. Needs: an open sketch with entities meeting at each corner ([x, y] in sketch mm). Changes: each corner becomes a line and the entities either side are trimmed back to it. Returns: chamfer with one id per corner, the corners and the sizes. A corner with no sketch point fails as invalid_input and nothing changes.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`corners` and `distance` (mm) are required; `distance2` (mm) or `angle` (degrees), not both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description goes well beyond them by disclosing what actually changes ("each corner becomes a line and the entities either side are trimmed back to it") and the atomic failure mode ("fails as `invalid_input` and nothing changes"). That failure/rollback guarantee is exactly the kind of behavioral detail annotations cannot convey.

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 organized under explicit Needs/Changes/Returns labels that map to prerequisite, side effect, and output. Every clause carries information; nothing is padding.

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 mutation tool with a nested-object schema and an output schema, the definition covers prerequisites, geometric effect, parameter combinations, and error behavior. Anything an agent needs to invoke it correctly and interpret a failure is present.

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 baseline is 3, but the description adds geometric meaning: `distance` alone cuts equal distances on both sides, `distance2` gives an asymmetric second side, and `angle` works in degrees with `distance`. The mutual exclusivity of distance2 and angle is restated from the schema, so the gain over structured fields is real but modest.

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 ("Bevel corners of the open sketch") plus the selection mechanism ("picking each corner by its point"). Explicitly distinguishes itself from the sibling `add_chamfer` by scope (2D profile vs. solid edges), so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool and the condition that selects it ("bevel a solid's edges with `add_chamfer` instead, last in the feature tree"). Adds prerequisites ("an open sketch with entities meeting at each corner") and parameter-selection guidance for distance vs. distance2 vs. angle, leaving little to inference.

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