Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

optimize_precast_manhole_elements

Decomposes manholes and road gullies into optimal precast concrete elements and generates a consolidated manufacturer RFQ bill of materials.

Instructions

[v0.2 Tool 7] Decompose manholes and road gullies into optimal precast concrete elements
(base AFE, cone ASZ or shallow flat slab AFT, shaft rings AGY 100/75/50/25 cm, adjustment rings SZB 60/10, 60/8, 60/6 cm,
and D400 covers/grates) and generate a consolidated manufacturer RFQ Bill of Materials (BOM).

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

Input Schema

NameRequiredDescriptionDefault
manholesNoExplicit list of manhole/gully specifications (node_id, cover_level_m, invert_level_m or total_depth_h1_m, nominal_diameter_mm, surface_type).
node_layersNoWhen file_path_cad is used, layers containing manholes/gullies.
text_layersNoWhen file_path_cad is used, layers containing level callout texts.
file_path_cadNoOptional path to a .dxf or .dwg file to automatically extract manholes and levels before optimizing precast rings.
catalog_profileNoPrecast element catalog: 'DIN_EN_1917_STD' (European EN 1917 / DIN 4034), 'ASTM_C478_US' (North American ASTM C478), or 'SZEBETON_T2_HU' (Hungarian SzeBeton T2).SZEBETON_T2_HU
unit_scale_to_meterNoWhen file_path_cad is used, CAD unit scale to meters (default 1.0).
default_surface_typeNoDefault surface finish for CAD-extracted manholes (PAVING_BLOCK selects 600x600mm D400 HYDROTEC square-frame cover).ASPHALT_OR_ROAD
cover_frame_height_cmNoCast-iron cover frame height in cm deducted from total depth h1 (default 17.0 cm: h2 = h1 - 17 cm).
spare_adjustment_ring_per_manholeNoIf True (default), adds +1 pc of SZB 60/10 adjustment ring per circular manhole to the order BOM.

Output Schema

NameRequiredDescriptionDefault
warningsNo
assembliesNo
gullies_countYes
manholes_countYes
catalog_profileYes
consolidated_bomNo
shallow_flat_slab_countYes
total_structures_processedYes

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 provided, so the description carries the full disclosure burden. It does reveal real behavioral content beyond the name: the decomposition is 'optimal', it emits an RFQ-oriented BOM for a manufacturer, and it names the element catalog families used. It does not say what happens if neither a manhole list nor a CAD path is given, whether anything is written to disk, or that results depend on the chosen catalog profile.

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 with the verb and outcome first, followed by the element enumeration. The dense parenthetical list earns its place by defining the output BOM vocabulary, though the '[v0.2 Tool 7]' prefix is noise that does not help an agent.

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?

For a 9-parameter, annotation-free tool the description covers purpose and output (and an output schema exists, so return shape need not be restated). It omits the input-mode contract — explicit manhole list versus CAD extraction, and that at least one is effectively required — which is the main thing an agent needs before calling it correctly.

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 is already documented in the schema; the baseline of 3 applies. The description adds domain vocabulary (AFE/ASZ/AFT/AGY/SZB sizes) that helps interpret the catalog_profile and ring options, but it adds no parameter-level detail such as elevation precedence or unit-scale effects beyond what the schema states.

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 opens with a specific verb and resource ('Decompose manholes and road gullies into optimal precast concrete elements') and adds a concrete secondary outcome ('generate a consolidated manufacturer RFQ Bill of Materials'). It also enumerates the exact element families (AFE, ASZ/AFT, AGY, SZB, D400), which pins down the domain. It stops short of naming a sibling to contrast with, so a 4 rather than 5.

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: the description tells you what the tool produces but never states when to reach for it versus QTO/BOQ siblings, nor any prerequisite (e.g. that a catalog profile or at least one of the manhole list / CAD file must be supplied). An agent can infer the context from the resource type, but there is no explicit when-to-use or when-not guidance.

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