civilquants.com

CivilQuants — QS-grade parametric estimating engine. Exposes 46 compute_<slug> tools (one per assembly), a render_skill_report tool for BoQ deliverables (Excel + Word), four project tools (save_project, get_project, list_projects, recompute_project) for paid-tier subscribers, and ten senior-QS skill methodologies (tender review + risk, QS measurement/contract advice, geotechnical + geo-environmental interpretation, earthworks, preliminaries, pavement design, subcontract analysis) reachable via the list_skills + get_skill tools (paid tier). The document-heavy skills require a code-execution client (Claude Code / Codex / VS Code) and the chunking pack from get_document_pipeline to run a real tender pack — on a chat connector you can read the methodology but cannot chunk/parse documents; the Word adjudication pack renders customer-side via word-report-base (get_document_pipeline component='render'), not server-side. Anonymous callers may use the six free-tier compute tools (attenuation_tank, cantilever_wall, end_area_earthworks, gully, headwall, manhole) and the Excel render skill — all other tools return a TIER_INSUFFICIENT envelope until OAuth-based subscription resolution lights up. The free tier renders the MMHW standard only; CESMM4, NRM2 and SMM7 require a paid tier. Saved projects: save_project creates a new project each call; to revise a parameter, fetch the stored assemblies with get_project, amend them, call save_project again (suffix the name, e.g. 'R02'), then recompute — recompute_project takes no parameter overrides. In a later conversation, re-find saved work with list_projects or get_project by exact name. Pass deliverables=["xlsx","dxf","pdf"] (any subset) on a compute call for one-shot download URLs: Excel BoQ (both tiers) plus dimensioned DXF + PDF drawing sheets (paid tier). For linear assemblies (pipe runs, kerbs, drains, barriers, channels), always confirm the run length with the user before computing — quantities scale directly with it and an unstated run length is the most common source of error. Read civilquants://intro for positioning and the free/paid boundary, and civilquants://catalogue for the full assembly picker with tiers. A compute response is large; pass output_mode='summary' or 'boq' to get a trimmed payload in chat (default returns the full result). For a procurement take-off (what to order — the aggregate quantity of each material, no priced bill), pass output_mode='material_schedule'. Trimmed modes null already-computed fields (the dimensioned drawing, the audit trail, sometimes the bill rows) to save tokens — that is paring, NOT a missing capability; _meta.output_mode lists what was omitted and the mode that returns it. Example: "Measure a 1200 mm manhole 3 m deep to MMHW." Not sure which tool to call? Describe the job in words and call resolve_assembly_from_description — it routes you to the right assembly and lists the fields you'll need, then you call compute_<slug>.