Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Update Title Block

update_title_block
Idempotent

Updates title-block fields for title, drawing number, drawn by, date, revision, and company on the active SolidWorks drawing; unspecified fields keep their values.

Instructions

Change the active drawing's title-block fields: title, drawing number, drawn by, date, revision, company.

Each field is written to the property the sheet format shows (the same mapping generate_drawing_package uses): the title is the drawn model's Description, the others the drawing's own properties. Fields not given keep their values. Needs: an open, active drawing of a model. Changes: those properties. Returns: fields, each with the property written, on (drawing or model) and value.

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": {
      "input_data": "<input_data>"
    },
    "name": "update_title_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesAt least one of `title`, `drawing_number`, `drawn_by`, `drawn_date`, `revision`, `company`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantive behavior beyond the annotations: which underlying property each field writes (title goes to the model's Description, others to the drawing's own properties), that omitted fields are preserved, and that changes are non-destructive edits rather than rebuilds. This property-mapping detail is non-obvious and would otherwise cause silent mistakes.

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-loads the action and fields, then uses compact Needs/Changes/Returns clauses, so the agent can scan it quickly. The Returns sentence is somewhat redundant given an output schema exists, and the parenthetical mapping note is dense, but nothing 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?

For a mutation tool with annotations, a fully described nested schema, and an output schema, the description supplies the remaining essentials: prerequisites, exactly what is mutated, partial-update safety, and a pointer to the 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.

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, but the description adds meaning the schema does not fully carry — the shared mapping convention with generate_drawing_package and the fact that unspecified fields are left untouched. It largely restates the per-field descriptions rather than adding syntax or format guidance.

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 ('Change the active drawing's title-block fields') and enumerates exactly which fields are involved. It is clearly differentiated from format-level siblings such as update_sheet_format and from the package-level generate_drawing_package, whose mapping it explicitly parallels.

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 precondition ('Needs: an open, active drawing of a model') and clarifies partial-update behavior ('Fields not given keep their values'), which tells the agent this is safe to call incrementally. It does not explicitly say when to prefer a sibling (e.g. update_sheet_format) instead, so it stops short of full when/when-not guidance.

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