Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

create_drawing

Generate a drawing sheet from a saved part or assembly with front, top, side and optional isometric views plus model dimensions, automatic scale, and first- or third-angle projection.

Instructions

Create a drawing of a saved part or assembly: front, top and side views, optionally an isometric view and the model's dimensions. The scale is chosen automatically unless given. end_view picks which end of the model the side view shows; spread (on by default) spaces the views evenly over the sheet. Save it with save_document (a .SLDDRW path keeps the drawing) and export it with export_pdf; list_drawing_views shows what is on the sheet. For a model whose 'up' is +Z give front_direction {x:0, y:-1, z:0} and up {x:0, y:0, z:1}: the other views are projected from the main one, the isometric view gets the same 'up', and the automatic scale fits the views on the sheet. The model file is not changed.

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": {
      "projection": "<projection>"
    },
    "name": "create_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
upNoThe model axis that points up in the main view
scaleNoe.g. '1:2' or '2:1' (default: automatic)
spreadNoSpread the views over the sheet with equal gaps and the largest standard scale that fits (false = packed in a corner)
end_viewNoWhich end of the model the projected end view shows (a standard view around the main one, e.g. left or right)
isometricNoAdd an isometric view
dimensionsNoBring the model's dimensions into the views (off by default: dimensions added later with add_drawing_dimension would appear twice)
model_pathNoThe .SLDPRT / .SLDASM file to draw (default: the active document, which must be saved)
projectionYesfirst = ISO / Europe, third = ANSI / US
sheet_sizeNoSheet size, landscapeA3
front_directionNoWhere the camera of the main view is, seen from the model, along a model axis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that the model file is not changed, that the active document must be saved when model_path is omitted, how the automatic scale fits the sheet, and why dimensions default off. It omits error/permission behavior and what the call returns, keeping it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core operation, then parameter semantics, then follow-ups; nearly every sentence earns its place. The +Z coordinate example is dense but justified, though sheet_size is never mentioned, leaving the coverage slightly uneven.

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 10-parameter tool with nested objects and no output schema, the description covers most semantics including the nontrivial direction/up interaction and non-destructive guarantee. It leaves sheet_size and projection unaddressed in prose (relying on the schema) and says nothing about the return value.

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; the description nonetheless adds real meaning by explaining end_view's role, spread's default effect on layout, and a concrete front_direction/up example for +Z-up models showing how the views are projected.

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 ('Create a drawing of a saved part or assembly') plus the exact scope: front, top, side, optional isometric and dimensions. This clearly distinguishes it from sibling view-creation tools such as create_exploded_view or add_section_view.

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 explicit follow-up routing: save with save_document, export with export_pdf, inspect with list_drawing_views, and notes dimensions added later via add_drawing_dimension would duplicate. It never says when NOT to use this tool or names a competing drawing-creation path, so it falls 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