Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Set Sheet Scale

set_sheet_scale
Idempotent

Adjust the active drawing sheet’s scale, such as 1:2, so sheet-scale views resize with it. Use it when views are too large for the sheet or dimensions overlap.

Instructions

Set the active drawing sheet's scale, e.g. 1:2; views that use the sheet scale follow it.

Use it when views are too large for the sheet, or when arrange_dimensions reports overlaps it can't clear. Needs: an open, active drawing. Changes: the sheet scale. Returns: data with the sheet name and the new scale.

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": "set_sheet_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoThe scale. `numerator` and `denominator` are required and must be above zero, e.g. 1 and 2 for 1:2.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare non-read-only, idempotent, non-destructive, so the description is not carrying the safety burden alone — but it still adds real value by disclosing the cascade ('views that use the sheet scale follow it'), the open-document prerequisite, and the returned payload. It does not state how views with an overridden scale behave, which is the one behavioral gap an agent might care about.

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?

The outcome sentence is front-loaded, then a compact Needs/Changes/Returns block. Every line carries distinct information; nothing is redundant with the schema or annotations.

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?

With annotations covering the safety profile and an output schema present, the description fills the remaining gaps: prerequisite state, side effects, and a one-line return shape. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100% and the single nested object already documents numerator/denominator with examples and exclusiveMinimum constraints. The description's 'e.g. 1:2' adds nothing the schema does not, so this is the baseline case where structured fields do the work.

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 ('Set the active drawing sheet's scale') plus the scope consequence that views inheriting the sheet scale follow it. An agent can distinguish this from sheet-format or component-state siblings, though it never explicitly contrasts itself with update_sheet_format, which is the nearest-sounding neighbor.

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 concrete trigger conditions ('views are too large for the sheet', or 'arrange_dimensions reports overlaps it can't clear') and states the prerequisite of an open, active drawing. It stops short of an explicit when-not-to-use rule or a named alternative for changing an individual view's scale, so it is clear context rather than full routing.

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