Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Detail View

create_detail_view

Create a magnified detail view from a circular area of an existing drawing view at a specified scale and sheet position.

Instructions

Magnify a circular area of a drawing view as a detail view, at a scale.

Give the circle's centre (sheet mm, inside the view) and radius, where the new view goes, and its scale. A centre outside the view or a position off the sheet is refused before anything changes. Needs: an open, active drawing with that view. Changes: adds a detail view and its circle. Returns: view with name, label, scale, 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_detail_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe detail. `view`, `center`, `radius` and `position` are required; `scale` is 2:1 and `label` the next free letter.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, non-idempotent, non-destructive write. The description adds real behavioral context: changes are validated atomically ('refused before anything changes'), required document/view state, exactly what is created (the view and its circle), and the returned fields. That is well beyond the annotation coverage.

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 action, then inputs, then preconditions, then effects and return shape, using terse labeled clauses ('Needs:', 'Changes:', 'Returns:'). No sentence is filler and nothing important is buried.

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 nested-object mutation tool with an output schema, the description covers the preconditions, defaults (scale 2:1, auto label), validation failure behavior, and side effects — everything an agent needs to decide and call correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description reinforces units (sheet mm), the 'inside the view' constraint on center, and the sheet-bound constraint on position, but adds little that the per-parameter descriptions do not already state.

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 opening sentence names a specific verb (magnify), a specific resource (a circular area of a drawing view) and the exact artifact produced (a detail view at a scale). The 'circular area' framing naturally separates this from the section/exploded view siblings without needing to name them.

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?

'Needs: an open, active drawing with that view' gives a clear precondition, and the refusal rule ('a centre outside the view or a position off the sheet is refused') tells the agent when the call will fail. It stops short of explicit alternatives, e.g. routing to create_section_view when a cut rather than a magnified circle is wanted.

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