Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

export_qto_visual_overlay

Export an interactive HTML/SVG visual verification map of measured polygons, deducted islands, linear features, and point nodes with IDs and m²/m quantities for QTO review.

Instructions

[v0.3 Tool 12] Export an interactive HTML and SVG visual verification map showing all measured
polygons, deducted islands, linear features, and point nodes labeled with their IDs and m2/m quantities.

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": {
      "file_path": "<file_path>"
    },
    "name": "export_qto_visual_overlay"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoUI language for the generated HTML and SVG report ('en', 'de', or 'hu').en
file_pathYesAbsolute path to the DXF or DWG file.
output_dirNoOptional directory for the generated .html and .svg files.
point_layersNoPoint/circle/insert layers (manholes, bollards) to render as markers.
linear_layersNoLinear layers (curbs, pipes, edges) to render and label with length (m).
boundary_layersNoPolygon boundary/hatch layers to render as filled net area surfaces.
island_hole_layersNoIsland/deduction layers to subtract and highlight in dashed red.
unit_scale_to_meterNoMultiplier converting CAD drawing units to meters.

Output Schema

NameRequiredDescriptionDefault
warningsNo
output_svg_pathYes
source_dxf_pathYes
output_html_pathYes
total_net_area_m2Yes
unit_scale_to_meterYes
rendered_lines_countYes
rendered_points_countYes
total_linear_length_mYes
rendered_polygons_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does carry the full burden, and it does disclose the output artifacts (interactive HTML plus SVG) and how features are rendered/labeled, including dashed red deduction islands. It does not say whether it re-reads and re-measures the CAD file (file_path is required, suggesting it does its own extraction), whether existing files in output_dir are overwritten, or what happens when layer parameters are omitted.

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?

A single, front-loaded sentence that names the deliverable and its contents with no filler. The '[v0.3 Tool 12]' prefix is internal bookkeeping noise that does not help an agent select the tool, which keeps it from a 5.

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?

An output schema exists, so return values need not be described, and all 8 parameters are fully documented in the schema. However, for a tool that writes files to disk, the description omits default output location behavior, overwrite semantics, and whether measurement is recomputed or reused, leaving real gaps for a moderately complex exporter.

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 the schema already explains every parameter including layer filters, locale and unit_scale_to_meter. The description only groups the rendered entity categories (polygons, islands, linear, points), which loosely mirrors the layer parameters but adds no syntax, defaults or interaction behavior. Baseline 3 applies since the schema does the heavy lifting.

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 and artifact: exports an interactive HTML/SVG visual verification map of measured polygons, deducted islands, linear features and point nodes with IDs and m2/m labels. That is far more concrete than a restated name and no sibling tool in the list produces a visual overlay. Sibling differentiation is implicit (it is the only rendering/export tool) rather than stated.

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?

The phrase 'visual verification map' implies it is used to visually check measurements after quantity takeoff, but there is no explicit when-to-use or when-not-to-use guidance and no named alternatives among the many QTO siblings. An agent can infer the workflow position but must guess whether it should be called before or instead of the measure/calculate tools.

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