Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

move_drawing_view

Move a drawing view so its outline center lands at given sheet coordinates; projected views follow, alignment can be kept or broken, and off-sheet or overlapping placements are flagged.

Instructions

Move a drawing view so that its outline centre (see list_drawing_views) lands at x_sheet, y_sheet (mm from the lower left corner). Projected views follow. A view aligned to its parent moves only along that alignment unless keep_alignment is false, which breaks it. Refused if a moved view would leave the sheet. Warns, naming them, when the moved view now overlaps other views.

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_sheet": "<x_sheet>",
      "y_sheet": "<y_sheet>"
    },
    "name": "move_drawing_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 (list_drawing_views)
x_sheetYesNew centre of the view's outline, from the left edge (in unit, mm by default)
y_sheetYesNew centre of the view's outline, from the bottom edge (in unit, mm by default)
keep_alignmentNofalse = break the alignment to the parent view and move freely

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses that child/projected views move with the parent, that alignment constrains motion along one axis unless broken, that out-of-sheet moves are refused outright, and that overlaps produce a warning naming the offending views. That is real consequence disclosure for a mutation. It omits whether the move is undoable and what a successful call returns.

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?

Four sentences, front-loaded with the primary action and target coordinates, followed by propagation, alignment and failure behavior in descending order of importance. No filler. The only blemish is the mm-specific phrasing in sentence one, which contradicts the general unit parameter and could mislead.

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?

No output schema and no annotations, so the description must carry behavior itself — and it covers propagation, alignment constraints, refusal and warning outcomes. For a 5-parameter mutation that is close to sufficient; what is missing is the successful return value and any document/context precondition.

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 every parameter is already documented, and the baseline is 3. The description does add coupling semantics not present in the schema (alignment determines which axis can move, and keep_alignment breaks it), but it also hardcodes '(mm from the lower left corner)' while the unit parameter permits cm, m, inch and ft — a mild inconsistency rather than added clarity.

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 (Move) and resource (a drawing view), then defines the exact target semantics: the outline centre landing at x_sheet, y_sheet measured from the lower left corner. It also points to list_drawing_views for the centre reference, so an agent can distinguish this from move_component or view-creation siblings immediately.

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 clear operating context: projected views follow, aligned views are constrained, and keep_alignment=false is the escape hatch. It implicitly tells the agent to call list_drawing_views first for the view name. It stops short of stating explicit preconditions (e.g. an active drawing document must exist) or exclusions, so it is not a full when/when-not/alternatives statement.

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