Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_drawing_views

Lists drawing views, sheets, visible edges, points, and dimensions to get the IDs and view coordinates needed for adding dimensions or section and detail views.

Instructions

List the views of the active drawing: name, type, scale, place on the sheet and number of dimensions. Given a view name it also lists that view's visible edges (E1, E2, ...), points (P1, P2, ...) and dimensions. Those ids are what add_drawing_dimension takes, and the coordinates are what add_section_view and add_detail_view take. The coordinates are VIEW COORDINATES: mm on the model, x to the right and y up on the sheet, measured from where the model origin appears in that view, independent of the view's scale and position. It also lists the sheets (name, size, views, dimensions, which is active). Changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_drawing_views"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoName of a view, e.g. 'Drawing View1' (default: list all views)

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?

With no annotations supplied, the description carries the full burden, and it does substantial work: 'Changes nothing' declares the read-only nature, and the coordinate paragraphs define the reference frame (mm on the model, x right, y up from the model origin, independent of scale and position). It does not say what happens when a view name is not found or when no drawing is active, which are the remaining behavioral gaps.

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?

It is front-loaded with the primary purpose and every sentence carries information about outputs or coordinate semantics. The coordinate explanation is dense and could be split into a shorter form, but no sentence is filler.

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?

There is no output schema and no annotations, so the description must describe return values, and it does so thoroughly for all three result sets (views, per-view edges/points/dimensions, sheets including which is active). Given a single-parameter list tool, an agent has enough to call it correctly and interpret the result.

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% and the schema already documents the single 'view' parameter and its default. The description adds real meaning beyond that by explaining what the parameter unlocks (visible edges, points, dimensions for that view) and reinforcing the default of listing all views, so it exceeds the baseline for a fully documented schema.

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 ('List the views of the active drawing') and enumerates the returned fields (name, type, scale, sheet placement, dimension count). It also discloses a second mode keyed on the view name (edges E1..., points P1..., dimensions) and a third result set (sheets), so an agent can tell exactly what this returns.

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?

It establishes the downstream workflow clearly: the edge/point/dimension ids are 'what add_drawing_dimension takes' and the coordinates are 'what add_section_view and add_detail_view take', which tells the agent to call this first. It stops short of explicit when-not guidance (e.g., versus list_edges or list_dimensions) and does not state prerequisites such as requiring an open drawing beyond the phrase 'active drawing'.

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