Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

add_section_view

Creates a section view in the active drawing by cutting an existing view along a straight line defined by two points, then places and labels the new view.

Instructions

Add a section view to the active drawing by cutting an existing view along a straight line. (x1, y1) and (x2, y2) are two points on the cutting line in view coordinates (mm on the model, from the model origin as seen in that view; see list_drawing_views); the cut runs the whole line, right across the view. A horizontal line puts the section below the view, a vertical one beside it, unless x_sheet / y_sheet (sheet mm) say otherwise; a default place that is taken or off the sheet moves to the nearest free place (along the alignment first, else anywhere, breaking the alignment). Returns the new view's name and label.

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>",
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "add_section_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesFirst point on the cutting line, x (view coordinates, in unit, mm by default)
x2YesSecond point on the cutting line, x
y1YesFirst point on the cutting line, y
y2YesSecond point on the cutting line, y
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 cut
labelNoSection letter (default: next free letter)
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

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses that the cut spans the entire line across the view, that placement is auto-derived from line orientation, and that a taken or off-sheet default silently relocates the view and may break alignment. It even states the return value (new view's name and label). It stops short of failure modes (e.g. a line that misses the view) or whether the operation is undoable.

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?

One front-loaded paragraph that leads with the action before unpacking coordinates and placement, with no filler sentences. The heavy parenthetical nesting makes it denser than it needs to be, but every clause carries information.

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 nine-parameter tool with no output schema, the description covers coordinate frame, placement behavior, fallback rules, and the return value, which is close to what an agent needs to call it correctly. Remaining gaps are edge cases rather than core mechanics.

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 coverage is 100%, so the baseline is 3; the schema already defines each of the nine parameters including units and defaults. The description does add real meaning — that x1/y1/x2/y2 are model coordinates as seen in the cut view rather than sheet coordinates, and that x_sheet/y_sheet are sheet millimetres — but it does not cover the optional label or unit parameters.

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?

Names a specific verb and resource ('Add a section view') and states the mechanism ('cutting an existing view along a straight line'), which is enough to tell it apart from a detail or exploded view in practice. It never names a sibling (e.g. add_detail_view) to make the distinction explicit, so it stops short of the top band.

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?

Usage is implied rather than stated: the agent learns it needs an existing view, and is pointed to list_drawing_views to obtain view coordinates, and the auto-placement rules are described. There is no explicit when-to-use vs. when-not, and no named alternative (such as a detail view) for the non-straight-cut case.

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