Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

List Drawing Views

list_drawing_views
Read-onlyIdempotent

Lists named views on the active SolidWorks drawing so you can identify valid view names before inserting dimensions, center marks, or other view-specific operations.

Instructions

List the views on the active drawing, by name.

Use it before auto_center_marks, insert_model_dimensions or any tool that takes a view name. Needs: an open, active drawing. Read-only. Returns: views (names, sheet formats left out) and count.

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

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description is not required to carry the safety profile. It still adds value beyond them by disclosing the environment prerequisite (an open, active drawing) and clarifying that sheet formats are excluded from the returned view list — a real behavioral detail about what data is and isn't surfaced.

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 short sentences, front-loaded with the action and scope, then the usage routing, then the requirement and return summary. Every sentence carries distinct information with no 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?

For a zero-parameter listing tool with full annotation coverage and an output schema present, the description supplies the missing non-schema essentials: the prerequisite state and the call-ordering guidance relative to tools that consume view names. Nothing an agent needs in order to call this correctly is absent.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline is 4. The description does not fabricate or misdescribe any inputs, and the implicit dependency on 'active drawing' state is covered as a precondition rather than a parameter.

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?

States a specific verb and resource ('List the views on the active drawing') plus a scoping detail ('by name'), which tells an agent exactly what comes back and distinguishes it from heavier analyzers in the sibling list. It stops short of explicitly naming what it is not (e.g., analyze_drawing_views), so it is clear but not fully differentiated.

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 a concrete usage context — call it before `auto_center_marks`, `insert_model_dimensions`, or any tool that takes a view name — and states the prerequisite of an open, active drawing. There is no explicit when-not-to-use guidance or reference to alternative listing/analysis tools, which keeps it at 4 rather than 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