Skip to main content
Glama

Set Title Block

set_title_block
Destructive

Populate or override a drawing page's title block fields—project, part, revision, date, material, and drawn-by—before exporting to SVG or PDF.

Instructions

Populate the drawing's title block (composed bottom-right on SVG/PDF export; calling this opts the page into rendering it). Scale, sheet size, units and part name are auto-derived; these fields override or add to them. Returns {handle, name, fields}.

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": {
      "page": "<page>"
    },
    "name": "set_title_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
revNo
dateNo
pageYes
partNo
unitsNo
projectNo
drawn_byNo
materialNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare mutation and destructive behavior, and the description adds real context on top: scale/sheet size/units/part name are auto-derived and these arguments override them, and calling the tool opts the page into title-block rendering on export. It returns {handle, name, fields}. It stops short of warning what happens to previously set fields, which is the main residual gap for a destructiveHint tool.

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?

Two sentences, front-loaded on the action and scope, with the export/rendering side effect and return shape packed in without waste.

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?

No output schema exists, and the description supplies the return shape, the auto-derivation behavior, and the export-time side effect — enough for an agent to call it correctly. A note on overwrite semantics for existing title-block entries would close the remaining gap.

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 only 11%, so the description has to carry weight. It does explain the override relationship for units/part and the auto-derivation of scale and sheet size, but rev, date, drawn_by, project, page and material get nothing beyond their names.

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 — populate the drawing's title block — and adds where it renders (bottom-right on SVG/PDF export). It is distinguishable from drawing siblings like add_annotation and make_drawing_page, though it never names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance, and no alternatives named. The only usable cue is the implied 'calling this opts the page into rendering it', which is a side effect rather than routing advice.

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