Skip to main content
Glama

Make Drawing Page

make_drawing_page

Creates a TechDraw drawing page with a default A4 landscape template or a custom SVG template, providing a starting layout for technical drawings.

Instructions

Create a TechDraw page using a built-in A4 landscape template by default. template: optional absolute path to a .svg template.

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

Input Schema

NameRequiredDescriptionDefault
nameNoPage
templateNo
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds the default-template behavior (built-in A4 landscape), which is genuine context beyond the schema. It does not say what happens if a page already exists, what the page is named/returned, or any document-state requirements.

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?

Two short sentences, front-loaded with the core action and default, followed by a targeted parameter note. No wasted text, though the template note could be folded more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with annotations covering safety and no output schema, the definition is minimally adequate but omits meaningful gaps: the role of the 'name' parameter, what is returned (page handle/name), and document-state prerequisites. An agent can call it, but with some uncertainty.

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 coverage is only 33%, so the description carries more burden. It explains the 'template' parameter as an optional absolute path to a .svg, which compensates for one undocumented param, but leaves 'name' (default 'Page') unexplained. Partial compensation warrants a middle score.

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+resource: 'Create a TechDraw page' with a default A4 landscape template. An agent can tell this is the page-creation step versus siblings like fit_page, export_drawing, or add_projection_group. No explicit sibling differentiation, but the action is unambiguous.

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?

The description never states when to use this tool versus alternatives, nor any prerequisites (e.g., an active document must exist, or that this should be called before add_projection_group/add_dimension). Usage is only inferred from the name.

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