Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

document_export_pdf

Export the active AutoCAD drawing or a chosen layout to an allowed PDF path for vector deliverables. Use this when you need a plotted PDF file rather than a raster screenshot.

Instructions

Export the active document or selected layout to an allowed PDF path; this writes an artifact and may require live AutoCAD plotting capability.

Side-effects: Writes PDF artifact to disk. Disambiguation: Use for vector deliverable export; use view_screenshot for quick raster inspection.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAllowed destination filesystem path (.pdf) for exported drawing
layoutNoOptional layout name to plot (e.g. 'Model' or 'Layout1'); defaults to active

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / layout / description
      Added value: +"Optional layout name to plot (e.g. 'Model' or 'Layout1'); defaults to active"
    • addedInput schema / properties / path / description
      Added value: +"Allowed destination filesystem path (.pdf) for exported drawing"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false; the description goes further by naming the concrete side effect (writes a PDF artifact to disk) and the environmental prerequisite (may require live AutoCAD plotting capability), which materially affects whether the call will succeed. It also flags that the path must be 'allowed', signaling a path policy check before invocation.

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 short labeled segments — core action, side effect, disambiguation — with the action front-loaded and zero filler. Every sentence carries a distinct piece of decision-relevant information.

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?

Output schema exists so return values need no explanation, and schema coverage handles parameters; what remains for the description — write side effect, plotting dependency, path restriction, and sibling routing — is all present. Nothing needed to invoke it correctly is missing, aside from overwrite behavior, which is a minor omission.

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 100%, so both 'path' and 'layout' are already documented, including the default-to-active behavior. The description's phrase 'selected layout' echoes rather than extends the schema, so this is the baseline-3 case where structured fields do the work.

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 (Export) plus resource (active document or selected layout) and the output format (PDF), which is exactly what the name promises. The disambiguation line separates it from the raster sibling view_screenshot, so an agent can pick between them without inspecting either schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative (view_screenshot) and the condition that selects it (quick raster inspection vs. vector deliverable export). This is the when-to-use-this-versus-that guidance most definitions omit.

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