Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

extract_longitudinal_profile_data

Computes trench excavation, machine/hand split at utility crossings, two-sided shoring area, and C12/15 concrete encasement volumes from utility longitudinal profile data.

Instructions

[v0.3 Tool 10] Analyze a utility longitudinal profile (hossz-szelvény) to compute trench excavation,
machine vs. hand excavation split at utility crossings, two-sided shoring area, and shallow-cover
(<1.00 m) C12/15 concrete encasement volumes.

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": "extract_longitudinal_profile_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxf_pathNoOptional path to a longitudinal profile DXF to auto-extract station bands.
stationsNoOrdered list of profile station points (chainage, ground level, invert level).
crossingsNoList of utility crossings along the profile requiring hand excavation.
profile_nameNoIdentifier or title of the longitudinal profile (hossz-szelvény).Utility Longitudinal Profile
bedding_thickness_mNoBedding thickness below pipe invert in meters (default 0.15m).
min_cover_threshold_mNoMinimum crown cover threshold in meters below which C12/15 concrete encasement is required (default 1.00m).
nominal_diameter_dn_mmNoNominal pipe diameter DN in mm (e.g., 160, 200, 300).
trench_width_override_mNoOptional explicit trench width in meters (overrides DIN 4124 / EN 1610 auto-width).
side_cover_above_crown_mNoPipe-zone sand cover above pipe crown in meters (default 0.30m).
shoring_depth_threshold_mNoTrench depth threshold in meters above which two-sided shoring is calculated (default 1.25m).
concrete_encase_thickness_mNoConcrete encasement wall thickness around pipe in meters (default 0.15m).

Output Schema

NameRequiredDescriptionDefault
spansNo
stationsNo
warningsNo
profile_nameYes
trench_width_mYes
crossings_countNo
outer_diameter_mYes
total_backfill_m3Yes
hand_excavation_m3Yes
total_excavation_m3Yes
machine_excavation_m3Yes
min_cover_threshold_mYes
total_excess_spoil_m3Yes
total_shoring_area_m2Yes
nominal_diameter_dn_mmYes
total_profile_length_mYes
shoring_depth_threshold_mYes
total_bedding_and_zone_m3Yes
shallow_concrete_encase_m3Yes
total_pipe_displacement_m3Yes
shallow_protection_length_mYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden. It does disclose the computational behavior and one key threshold rule (shallow cover below 1.00 m triggers C12/15 encasement), which is genuinely useful. It does not state whether the tool is a pure calculation with no side effects, what happens when both dxf_path and stations are omitted, or how the auto-width/shoring rules interact.

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 dense sentence that front-loads the resource and then lists the four computed outputs, with zero filler. The '[v0.3 Tool 10]' version tag is internal noise that costs a little clarity but not comprehension.

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 and the input schema is fully annotated, so the description does not need to explain return values or individual fields. What it is missing for an 11-parameter tool with no annotations is the input-mode contract: either dxf_path for auto-extraction or stations for manual input.

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% and each of the 11 parameters is well documented, including defaults for bedding, shoring threshold, and encasement thickness, so the baseline is 3. The description corroborates only the 1.00 m cover threshold and the crossing-based hand excavation; it adds no new parameter semantics such as how trench_width_override_m interacts with the DIN 4124 auto-width.

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 uses a specific verb-and-resource pair ('Analyze a utility longitudinal profile') and enumerates the concrete quantities produced: trench excavation, machine vs. hand split at crossings, two-sided shoring area, and shallow-cover concrete encasement. It is clearly not a generic QTO tool, but it never contrasts itself with siblings like calculate_pavement_layer_quantities or measure_linear_and_area_features, so the differentiation is left implicit.

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

Usage Guidelines2/5

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

There is no statement of when to choose this tool over a sibling, no precondition (e.g., that the profile must be a hossz-szelvény DXF or an explicit station list), and no exclusions. The only usage signal is the domain vocabulary itself, which an agent must infer.

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