Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Section View

create_section_view

Cut a section view along a line across an active SolidWorks drawing view and place it on the sheet, rejecting lines that miss the view or positions off the sheet.

Instructions

Cut a section view along a line across a drawing view, and place it on the sheet.

Give the line's ends in sheet mm so it crosses the view (e.g. through a hole's centre), and where the new view goes. A line that misses the view, or a position off the sheet, is refused before anything changes. Needs: an open, active drawing with that view. Changes: adds a section view and its section line. Returns: view with name, label, parent and outline_mm.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe section. `view`, `line_start`, `line_end` and `position` are required; `label` defaults to the next free letter.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false); the description adds the meaningful extras: what gets created (view plus its section line), that validation happens "before anything changes," the prerequisite document state, and the exact return shape. It stops short of covering undo/reversibility or how repeated calls behave (consistent with idempotentHint=false, but that implication is left unstated).

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 imperative sentence followed by a terse Needs/Changes/Returns block; every clause carries information (units, constraints, defaults, return keys) with no restatement of the tool name or 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 one-parameter nested mutation on a complex CAD document, it covers prerequisites, validation failure behavior, side effects, and the returned fields; with an output schema present, no further explanation of return values is needed.

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 the baseline is 3, but the description earns more: it fixes the unit and frame for the coordinates ("sheet mm"), explains that the line ends must cross the view (e.g. through a hole's centre), clarifies that position is the new view's placement, and notes the label defaults to the next free letter.

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?

"Cut a section view along a line across a drawing view, and place it on the sheet" gives a specific verb (cut/place) and resource (section view) plus the defining mechanism — a section line crossing an existing view. That mechanism implicitly separates it from sibling creators like create_detail_view or create_exploded_view, but no sibling is named, so routing relies on the agent's own knowledge of the alternatives.

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?

Preconditions are stated explicitly ("Needs: an open, active drawing with that view") along with the rejection conditions (line missing the view, position off the sheet). It does not compare against or exclude sibling view-creation tools, so it reads as clear context rather than full when/when-not guidance.

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