Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

calculate_tin_earthwork_volumes

Compute 3D TIN earthwork volumes from CAD spot elevations or point clouds, including topsoil stripping, cut, fill, and net balance between existing terrain and design subgrade.

Instructions

[v0.5 Tool 16] Compute 3D Delaunay TIN surface earthwork volumes (topsoil stripping, cut, fill,
and net earth balance) between existing terrain and designed subgrade level directly from
CAD spot-elevation layers or 3D point clouds (without Civil 3D).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_tin_earthwork_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_pointsNoList of designed surface or subgrade spot elevation points (X, Y, Z in meters).
file_path_cadNoOptional DXF/DWG path to extract spot elevation points and boundary polygons.
boundary_layersNoCAD layers defining the earthwork/grading boundary polygon.
existing_pointsNoList of existing ground spot elevation points (X, Y, Z in meters).
unit_scale_to_meterNoCAD drawing unit scale to meters (default 1.0).
fill_compaction_factorNoCompaction multiplier for required borrow fill (default 1.15).
design_elevation_layersNoCAD layers containing designed surface elevation POINT/INSERT/TEXT entities.
existing_elevation_layersNoCAD layers containing existing ground elevation POINT/INSERT/TEXT entities.
topsoil_strip_thickness_mNoTopsoil stripping thickness in meters (e.g., 0.10m or 0.20m).
constant_design_elevation_mNoOptional constant horizontal design elevation [mBf] if `design_points` is not provided.
pavement_structure_thickness_mNoTotal pavement structure thickness (m) deducted from finished design surface to reach the subgrade mirror level (tükörszint). Pass 0.0 if design_points are already subgrade levels.

Output Schema

NameRequiredDescriptionDefault
warningsNo
cut_area_m2Yes
fill_area_m2Yes
avg_existing_z_mYes
avg_subgrade_z_mYes
max_existing_z_mYes
max_subgrade_z_mYes
min_existing_z_mYes
min_subgrade_z_mYes
compaction_factorNo
footprint_area_m2Yes
cut_volume_bank_m3YesNet excavation (bevágás) volume below stripped ground to subgrade level in m3.
design_points_countYes
tin_triangles_countYes
net_earth_balance_m3Yesfill_volume_required_bank_m3 - cut_volume_bank_m3 (negative = excess spoil to haul away; positive = borrow needed).
existing_points_countYes
topsoil_strip_volume_m3Yes
fill_volume_compacted_m3YesNet embankment/fill (töltés) volume above stripped ground to subgrade level in m3.
topsoil_strip_thickness_mYes
fill_volume_required_bank_m3YesRequired borrow/bank fill volume including compaction factor (fill_compacted * compaction_factor).
pavement_structure_deduction_mYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the computation method (Delaunay TIN), the quantities produced, and that topsoil stripping and fill compaction are applied, which is useful beyond the schema; but it says nothing about failure modes (e.g., insufficient points, non-overlapping surfaces), whether any files are written, or precision expectations for a 3D volume computation.

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 leads with the verb and the deliverable, with no filler prose. The '[v0.5 Tool 16]' prefix and the parenthetical '(without Civil 3D)' are slight noise, but the content itself is dense and earns its place.

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 11 parameters are documented in the schema. Still, with zero required parameters, the description should say that at least one input source (existing_points or file_path_cad plus layers) is mandatory; that omission is the main completeness gap for an otherwise descriptive tool.

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% with 11 well-documented parameters, so the baseline is 3. The description adds only the framing that inputs come from CAD spot-elevation layers or point clouds and that the result is measured against a designed subgrade; it does not explain the interplay among file_path_cad, the layer lists, and the point arrays that an agent must choose between.

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?

The description names a specific verb ('Compute') and a precise resource ('3D Delaunay TIN surface earthwork volumes') and enumerates the outputs: topsoil stripping, cut, fill, net earth balance. That is far more specific than any sibling such as calculate_pavement_layer_quantities, though it never explicitly contrasts itself with them.

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?

It implies the two input routes ('directly from CAD spot-elevation layers or 3D point clouds') and the 'without Civil 3D' framing tells the agent this is a standalone alternative to Civil 3D workflows. However, it gives no explicit when-to-use vs. when-not guidance, no prerequisites, and no routing between the design_points and constant_design_elevation_m options.

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