Skip to main content
Glama
civil-qto-mcp

civil-qto-mcp

audit_technological_completeness

Audit a BoQ workbook for omitted items across six civil engineering completeness chains, then generate ready-to-insert supplemental item payloads.

Instructions

[v0.4 Tool 13] Audit a BoQ workbook against 6 civil engineering technological completeness chains
(asphalt, block paving, gravity sewers, pressure water lines, RC foundations, industrial slabs)
and generate ready-to-insert `BoQSupplementalItemInput` (K-tétel) payloads for omitted items.

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": {
      "boq_xlsx_path": "<boq_xlsx_path>"
    },
    "name": "audit_technological_completeness"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for generated supplemental item descriptions ('en', 'de', or 'hu').hu
sheet_namesNoOptional list of visible worksheet names to check.
boq_xlsx_pathYesAbsolute path to the BoQ Excel workbook (.xlsx / .xlsm) to audit.
cad_curb_length_mNoOptional CAD-measured curb length (m) to populate if curbs are missing from BoQ.
cad_asphalt_tie_in_length_mNoOptional CAD-measured asphalt tie-in length (m) for saw-cutting and joint sealing.
cad_shallow_pipe_concrete_m3NoOptional C12/15 concrete encasement volume (m3) for shallow pipes (<1.0m cover).

Output Schema

NameRequiredDescriptionDefault
findingsNo
warningsNo
file_pathYes
total_items_scannedYes
active_chains_detectedNo
missing_companions_countYes
ready_supplemental_itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does clarify that the tool produces 'ready-to-insert' payloads rather than silently mutating the workbook — an important behavioral signal. It still leaves unstated whether the workbook is written to, whether it must be closed/validated, and what happens when no omissions are found.

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 packs purpose, scope, and output into little space. The '[v0.4 Tool 13]' version prefix is non-functional noise, but it is the only clear waste.

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, so return values need not be explained, and the input schema is fully documented; the description supplies the domain framing (six chains) an agent needs to know this is a domain-specific audit. The main remaining gap is disambiguating this tool from the general BoQ auditor and clarifying side effects on the source workbook.

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 all six parameters (including locale enum and CAD measurement inputs) are already documented in the schema. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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 (audit), a specific resource (a BoQ workbook), and enumerates the six technological chains checked (asphalt, block paving, gravity sewers, pressure water lines, RC foundations, industrial slabs), plus the output artifact (BoQSupplementalItem payloads). It clearly differs from the generic 'inspect_and_audit_boq_xlsx' sibling by scope, though it never names that sibling to make the distinction explicit.

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 description implies the trigger condition (audit a BoQ for omitted technological items and generate K-tétel payloads), which is enough to infer when to call it. However, it gives no explicit when-not-to guidance and does not route the agent between this and the general workbook auditor or the various calculation siblings.

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