Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

calculate_pavement_layer_quantities

Calculate road and paving layer quantities in m2, m3, and metric tons while accounting for lateral step-out widening, compaction multipliers, and cutting or overlap waste.

Instructions

[v0.2 Tool 8] Calculate structural layer quantities (m2, m3, metric tons) for road and paving works,
accounting for lateral step-out widening beyond curb lines, compaction multipliers (e.g., CKT-4 x1.20),
and cutting/overlap waste.

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": {
      "net_surface_area_m2": "<net_surface_area_m2>"
    },
    "name": "calculate_pavement_layer_quantities"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_nameNoStandard pavement structure preset (used when `custom_layers` is not provided).LIDL_BBS_PARKING_PAVING
custom_layersNoOptional custom list of structural layers from top to bottom (overrides `preset_name`).
net_surface_area_m2YesNet surface area of the top pavement course in m2.
active_edge_perimeter_mNoOuter boundary perimeter (m) along which base courses widen laterally (step-out).

Output Schema

NameRequiredDescriptionDefault
layersNo
preset_usedNo
input_net_surface_area_m2Yes
total_structure_thickness_cmYes
input_active_edge_perimeter_mYes
total_subgrade_excavation_volume_m3Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal the calculation behavior (lateral step-out beyond curb lines, compaction multipliers, cutting/overlap waste), but says nothing about whether the tool is a pure stateless computation, how rounding or unit conversion to metric tons is handled, or what happens when optional factors are left at their defaults. For a numeric-calculation tool with zero annotation coverage, that leaves real gaps.

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 operation and enumerated behaviors, with no filler. The "[v0.2 Tool 8]" prefix is metadata noise that does not help an agent decide or invoke, which keeps it from a 5.

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?

The tool has one required parameter, a nested layer list, and an output schema, and the description covers the intended computation and its three adjustment mechanisms. Combined with the fully documented input schema, an agent has what it needs, though the absence of any statement about determinism or output units in prose leaves a small residual gap.

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 every parameter already documents itself, including the CKT-4 x1.20 compaction example and the 1.03 waste example. The description reinforces the parameter concepts but adds no format, unit, or coupling detail beyond the schema, so the 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?

The description gives a specific verb (calculate) plus resource (structural layer quantities) and names the output units (m2, m3, metric tons) and domain (road and paving works). That domain scoping is enough to separate it from siblings such as calculate_foundation_and_slab_qto and calculate_tin_earthwork_volumes without either schema being opened.

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 only implied by the phrase "for road and paving works"; there is no explicit when-to-use statement, no when-not condition, and no named alternative for adjacent tasks such as foundation/slab or earthwork volume takeoff. An agent can infer the fit, but must reason about it rather than being told.

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