Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_detail_view

Add an enlarged detail view to an active SOLIDWORKS drawing by placing a circle on an existing view and setting its own scale.

Instructions

Add a detail view to the active drawing: a circle on an existing view, shown enlarged at its own scale. The circle's centre (x, y) and radius are in view coordinates (mm on the model; see list_drawing_views). scale is the detail's own scale, e.g. '2:1' or '5:1' (default: twice the scale of the source view). Without x_sheet / y_sheet it goes beside the view, or to the nearest free place on the sheet. Returns the new view's name, label and scale.

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": {
      "view": "<view>",
      "x": "<x>",
      "y": "<y>",
      "radius": "<radius>"
    },
    "name": "add_detail_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesCircle centre x (view coordinates, in unit, mm by default)
yYesCircle centre y (view coordinates, in unit, mm by default)
unitNoUnit of the length inputs: mm (the default, whatever set_units says), cm, m, inch or ft. Results are in mm
viewYesName of the view to take the detail from
labelNoDetail letter (default: next free letter)
scaleNoScale of the detail view, e.g. '2:1' (default: twice the view's scale)
radiusYesCircle radius on the model (in unit, mm by default)
x_sheetNoCentre of the new view on the sheet, from the left edge (in unit, mm by default)
y_sheetNoCentre of the new view on the sheet, from the bottom edge (in unit, mm by default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does well: it discloses defaults for scale ('twice the scale of the source view'), for label placement, for sheet positioning, and for units, plus what is returned. It omits failure modes (nonexistent view name, out-of-range circle) and confirmation that the drawing is mutated, which keeps it below a 5.

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?

Three sentences, front-loaded with the action and mechanism, then defaults, then return value. Nothing is repeated and nothing is padding; a reader can act on the first sentence and refine with the rest.

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

Completeness4/5

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

For a 9-parameter mutation tool with no annotations and no output schema, the description covers defaults, coordinate spaces, placement fallback, and return contents — enough to call it correctly. Error behavior and any constraints on the circle relative to the parent view boundary are the only notable gaps.

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 adds genuine meaning: it clarifies that x/y/radius are in view coordinates on the model while x_sheet/y_sheet are on the sheet, and it explains the fallback placement when the sheet coordinates are absent — behavior the per-parameter schema text does not convey.

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 ('Add a detail view to the active drawing') and immediately defines the mechanism: 'a circle on an existing view, shown enlarged at its own scale.' That mechanism implicitly separates it from a section view or exploded view sibling, so an agent can pick it without opening another schema.

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?

Gives real operating context: the source view must already exist ('an existing view'), points to list_drawing_views for finding it, and explains what happens when x_sheet/y_sheet are omitted ('beside the view, or to the nearest free place'). It never states an explicit when-not or names an alternative tool, so it stops short of a 5.

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