Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_title_block

Places or updates a title block in the bottom right corner of the active drawing sheet, filling title, drawn by, date, scale, material and sheet size from the model on the first call.

Instructions

Put a title block in the bottom right corner of the active sheet, or update the one already there (title, drawn by, date, scale, material, sheet size; every input is optional). The first call fills missing fields from the drawing (title = the model's name, date = today, scale = the sheet scale, material = the drawn part's material, sheet size = the sheet); later calls change only the fields given. Returns the block as it now reads.

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_title_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate text, e.g. 2026-10-10
scaleNoScale text, e.g. 1:2
titleNoDrawing title
drawn_byNoWho drew it
materialNoMaterial text
sheet_sizeNoSheet size text, e.g. A3 (must be the real sheet size)

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 present, the description carries the burden well: it discloses default-source behavior per field (title from model name, date today, scale from sheet, material from the part, sheet size from the sheet), the patch-vs-fill semantics, and that the block is returned as it now reads. Remaining gaps are minor — no mention of failure modes when no drawing is active or whether the block's position is forced.

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 dense sentences with the primary action front-loaded, followed by default/update semantics and return value. No repetition of the schema, no filler.

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 six-parameter, all-optional mutation tool with no annotations and no output schema, the description supplies defaults, patch behavior, and a return-value summary — enough to call it correctly. It stops short of stating prerequisites (an open drawing/sheet) or error behavior.

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 earns extra credit by explaining where each omitted field's value comes from and by flagging the constraint that sheet_size must match the real sheet size. That default-source mapping is meaning the schema's per-property text does not convey.

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 (put a title block on the active sheet) and immediately clarifies the upsert case (or update the one already there). The enumerated field set makes it unambiguous which sibling concern this covers, versus set_material or set_units which touch different drawing properties.

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 clear operational context: the first call seeds missing fields from the drawing, later calls act as a partial update. It does not name alternatives or exclusions, but the title-block resource is distinct enough that none are obviously needed.

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