Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

convert_vector_pdf_to_dxf

Convert vector PDF civil engineering plans into layered DXF drawings and calibrate drawing scale from reference dimensions or title-block scale for accurate CAD takeoffs.

Instructions

[v0.3 Tool 9] Convert a vector PDF civil engineering plan into a layered DXF drawing via AutoCAD
Core Console (`_-PDFIMPORT`) and automatically calibrate `recommended_scale_factor_to_meters`
from reference dimensions, explicit scale denominator, or title-block scale text ('M=1:250').

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": {
      "pdf_path": "<pdf_path>"
    },
    "name": "convert_vector_pdf_to_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdf_pathYesAbsolute path to the vector PDF plan (or already imported DXF) to convert and calibrate.
page_numberNo1-based PDF page number to import.
output_dxf_pathNoOptional output DXF path. Defaults to system temp cache.
pdf_import_base_unitNoBase unit produced by PDF import (AutoCAD _-PDFIMPORT defaults to 'inch' = 0.0254m).inch
reference_cad_lengthNoOptional measured CAD length of a known dimension line for exact calibration.
reference_real_metersNoOptional real-world length in meters corresponding to `reference_cad_length`.
paper_scale_denominatorNoOptional explicit paper scale denominator (e.g., 250 for 1:250, 500 for 1:500).

Output Schema

NameRequiredDescriptionDefault
statusYes
warningsNo
page_numberNo
error_messageNo
output_dxf_pathNo
source_pdf_pathYes
converter_backendNoNONE
calibration_methodNoDEFAULT_UNSCALED
extracted_layer_countNo
extracted_entity_countNo
detected_scale_ratio_textNoScale ratio text found in title block or drawing annotations (e.g., '1:250', '1:500').
recommended_scale_factor_to_metersNoMultiplier to pass as `custom_scale_to_meter` to `measure_linear_and_area_features`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose real mechanism detail — external AutoCAD Core Console invocation, `_-PDFIMPORT`, and that scale calibration is auto-derived from one of three sources — which is valuable. It omits prerequisites (AutoCAD must be installed/licensed), failure behavior on non-vector or corrupt PDFs, and whether an existing `output_dxf_path` is overwritten.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded and compact, but the `[v0.3 Tool 9]` version tag and the heavy backtick/identifier formatting are internal noise that consume attention without aiding selection. One sentence of prerequisites could have replaced the tag at no extra cost.

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 7-parameter tool with an output schema, return values need not be explained and the core transform plus calibration logic are covered. What is missing is the operational envelope — environment dependency on AutoCAD, expected input fidelity, and the ordering rule for the three calibration routes — which matters for a tool that shells out to external software.

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 100% and every parameter already carries its own description, so the baseline is 3. The description adds modest meaning by grouping the calibration inputs into three conceptual routes (reference dimensions, explicit denominator, title-block text), but it never states the precedence among them when multiple are supplied.

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 precise verb and resource: converts a *vector* PDF civil engineering plan into a *layered* DXF drawing, and names the exact mechanism (`_-PDFIMPORT` via AutoCAD Core Console). The 'vector PDF' and 'layered DXF' qualifiers implicitly separate it from the sibling `convert_dwg_to_dxf`, so an agent can route on input format without opening a schema.

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

Usage Guidelines3/5

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

Usage is implied by the resource type (only usable on vector PDFs, not raster scans) and by the calibration sources listed, but there is no explicit when-to-use/when-not statement and no named alternative for adjacent tasks. The agent must infer that this is the ingestion entry point of a pipeline.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.