Skip to main content
Glama

Export Drawing

export_drawing
Destructive

Export a drawing page to PDF, SVG, or DXF headlessly, using the path extension to select the format. Returns the saved file path, size, format, view count, and dimensions.

Instructions

Export a drawing page to PDF, SVG, or DXF (format inferred from the path extension), headless. PDF/SVG are composed from the template, the per-view geometry, and any dimensions/annotations on the page; DXF uses FreeCAD's native page writer. Returns {path, size, format, views, dimensions}.

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>",
      "path": "<path>"
    },
    "name": "export_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
pathYes
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 declare readOnlyHint=false and destructiveHint=true; the description adds real context (headless execution, per-format composition method, return shape). The important gap is that it never says what makes this destructive — presumably overwriting an existing file at `path` — so the agent cannot judge the risk the annotation is warning about.

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?

Three compact sentences, purpose front-loaded, then format-specific mechanism, then return value — nothing redundant. Slightly dense but every clause carries information.

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?

No output schema exists, so the inline return-value sketch is a real contribution, and the format-inference rule is essential. Against that, a destructive write tool with two undocumented parameters and no stated overwrite behavior falls short of complete.

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 33% (only `workspace` is documented), so the description carries extra burden. It does add genuinely useful semantics for `path` — the output format is inferred from its extension — but `page` is never clarified (name vs. handle vs. object reference), and workspace behavior is unaddressed.

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 ('Export a drawing page') and pins down the supported formats (PDF, SVG, DXF) plus the format-inference rule, which is more than a restatement of the name. It does not name the nearby alternatives (render_view, render_views, sheet_flat_export, export_shape), so the boundary with those siblings is left to inference.

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?

There is no explicit when-to-use / when-not-to-use guidance and no prerequisites (e.g., that the page must already exist from make_drawing_page). The implied workflow ('composed from the template, the per-view geometry, and any dimensions/annotations') hints that it is a post-annotation step, but the agent must infer it.

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