Skip to main content
Glama
solidworks-mcp

solidworks-mcp

draft

Tilts selected faces by a specified angle around a neutral plane or face point to add mold-release geometry for casting or molding.

Instructions

Tilts faces by angle_deg (draft for moulding or casting), pivoting about a neutral plane: neutral_plane = "front", "top", "right" or a plane name, or neutral_face_point = a point on a planar face of the part (e.g. the parting face). face_points: a point on each face to tilt ([x, y, z] mm, model coordinates; see list_faces). flip reverses the pull direction.

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": {
      "angle_deg": "<angle_deg>",
      "face_points": "<face_points>"
    },
    "name": "draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNo
angle_degYesDraft angle in degrees
face_pointsYes
neutral_planeNo
neutral_face_pointNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent mutation. The description adds useful behavioral geometry details beyond annotations: pivoting about a neutral plane, neutral plane versus neutral face point options, and that flip reverses the pull direction. It still does not describe undo behavior or error conditions, but the output schema covers return values.

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 front-loaded with the operation and has no filler or redundant sentences. It is somewhat dense and semicolon-heavy, making the neutral-plane alternatives less scannable than a structured list would be.

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 five-parameter geometry mutation with low schema coverage, the description covers the core mechanics, required point inputs, coordinate system, and neutral-plane alternatives. Since an output schema exists, it does not need to explain return values.

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

Parameters5/5

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

Schema description coverage is only 20%, so the description must explain parameter meaning, and it does so for all five parameters. It clarifies angle_deg as the draft angle, face_points as one point per face in model coordinates, neutral_plane options, neutral_face_point as a point on a planar face, and flip as reversing pull direction.

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?

The description states a specific geometric operation: tilting faces by an angle for moulding or casting. It resolves the ambiguity of the tool name 'draft' and clearly identifies the resource being modified.

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?

It gives implied usage context by saying the operation is for moulding or casting, and it points to list_faces for obtaining face points. However, it does not explicitly say when to use this tool instead of other face-modifying siblings, nor does it state prerequisites or exclusions.

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