Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

convert_dwg_to_dxf

Convert a single .dwg file or an entire folder of .dwg files into .dxf format for CAD workflows, with optional version targeting, custom output directory, and cached conversions.

Instructions

[v0.2 Tool 6] Convert a single .dwg file or an entire folder of .dwg files into .dxf format.
Note: `inspect_civil_dxf`, `measure_linear_and_area_features`, and `extract_utility_network_and_levels`
also accept `.dwg` paths directly via transparent background caching.

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": {
      "source_path": "<source_path>"
    },
    "name": "convert_dwg_to_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
use_cacheNoIf True (default), reuses SHA-256 cached conversions.
output_dirNoOptional output directory for converted .dxf files. If None, writes side-by-side with source .dwg.
source_pathYesPath to a .dwg file or a directory containing .dwg files.
target_dxf_versionNoTarget AutoCAD DXF version (default 'R2018').R2018

Output Schema

NameRequiredDescriptionDefault
conversionsNo
total_filesYes
failed_countYes
succeeded_countYes
converter_backend_detectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose the background caching behavior and file-vs-folder handling, but says nothing about whether existing .dxf files are overwritten, where side-by-side output lands, or failure behavior on unreadable drawings. Useful but incomplete for a write-producing tool.

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 with the core capability front-loaded and the caveat second. The '[v0.2 Tool 6]' prefix is internal noise that costs a bit of signal, but the body has no wasted wording.

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?

An output schema exists, so return values need not be explained, and every parameter is described in the schema. What remains thin is the behavioral edge cases around overwriting existing .dxf output, but the core capability and the sibling caveat are covered.

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 all four parameters (source_path, output_dir, target_dxf_version, use_cache) are already documented in structured data. The description adds no format, version, or cache-invalidation detail beyond it, so baseline 3 applies.

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 and resource ('Convert a single .dwg file or an entire folder of .dwg files into .dxf format'), including the file-vs-folder scope in one sentence. The note about three sibling tools accepting .dwg directly further separates this conversion step from inspection/measurement/extraction tools.

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

Usage Guidelines4/5

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

The note implies when conversion is unnecessary, since inspect_civil_dxf, measure_linear_and_area_features, and extract_utility_network_and_levels consume .dwg via transparent caching. It does not explicitly state when a persistent .dxf is actually required, so guidance is clear but not a full when/when-not rule.

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