Skip to main content
Glama

PlanComply SANS 10400 Building Compliance

pre_check_building_plan

Run an automated multi-point regulatory validation on building plan or Pre-Council Concept Sketch specifications and return a compliance readiness score, defect warnings, Stage 4 roadmap, and municipal submission checklist.

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": {
      "municipality": "<municipality>"
    },
    "name": "pre_check_building_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
municipalityYesTarget South African municipality for plan submission (e.g. "City of Johannesburg", "Tshwane", "City of Cape Town", "Ekurhuleni", "eThekwini").
project_nameNoName of the building or architectural project.
building_classNoOccupancy classification (e.g. "H4 Single Dwelling House", "H3 Multi-Dwelling", "G1 Offices", "F1 Retail"). Default is "H4 Single Dwelling House".
has_sans_formsNoWhether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared.
submission_scopeNoOptional drawing stage scope: use "concept_sketch" for Pre-Council Client Floor-Plan Sketches before detailing sections/drainage, or "full_new_build" for complete council packs.
has_sacap_declarationNoWhether the drawing title block contains the registered architectural professional full name, registration number, category, and signature.
habitable_room_height_mmNoSpecified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm).
has_rodding_eyes_at_bendsNoWhether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions.
external_wall_thickness_mmNoExternal wall thickness in millimetres (standard cavity wall is min. 270 mm).
has_renewable_water_heatingNoWhether min. 50% solar water heating or heat pump is specified as required by SANS 10400-XA.
gully_height_above_ground_mmNoHeight of sewer gully head coping above finished ground level in millimetres (min. 150 mm).
has_safety_glass_below_800mmNoWhether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / submission_scope
      Added value: +{
      +  "description": "Optional drawing stage scope: use \"concept_sketch\" for Pre-Council Client Floor-Plan Sketches before detailing sections/drainage, or \"full_new_build\" for complete council packs.",
      +  "enum": [
      +    "concept_sketch",
      +    "full_new_build",
      +    "addition_alteration",
      +    "internal_fitout",
      +    "specialist_sheet",
      +    "hoa_submission"
      +  ],
      +  "type": "string"
      +}
  2. Changed9 schema fields changed
    • changedInput schema / properties / external_wall_thickness_mm / description
      Previous value: -"External wall thickness in millimetres (standard cavity wall is min. 270 mm). [Optional: omit to use server default filter]."New value: +"External wall thickness in millimetres (standard cavity wall is min. 270 mm)."
    • changedInput schema / properties / gully_height_above_ground_mm / description
      Previous value: -"Height of sewer gully head coping above finished ground level in millimetres (min. 150 mm). [Optional: omit to use server default filter]."New value: +"Height of sewer gully head coping above finished ground level in millimetres (min. 150 mm)."
    • changedInput schema / properties / habitable_room_height_mm / description
      Previous value: -"Specified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm). [Optional: omit to use server default filter]."New value: +"Specified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm)."
    • changedInput schema / properties / has_rodding_eyes_at_bends / description
      Previous value: -"Whether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions. [Optional: omit to use server default filter]."New value: +"Whether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions."
    • changedInput schema / properties / has_sacap_declaration / description
      Previous value: -"Whether the drawing title block contains the registered architectural professional full name, registration number, category, and signature. [Optional: omit to use server default filter]."New value: +"Whether the drawing title block contains the registered architectural professional full name, registration number, category, and signature."
    • changedInput schema / properties / has_safety_glass_below_800mm / description
      Previous value: -"Whether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL. [Optional: omit to use server default filter]."New value: +"Whether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL."
    • changedInput schema / properties / has_sans_forms / description
      Previous value: -"Whether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared. [Optional: omit to use server default filter]."New value: +"Whether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared."
    • changedInput schema / properties / municipality / description
      Previous value: -"Target South African municipality for plan submission (e.g. \"City of Johannesburg\", \"Tshwane\", \"City of Cape Town\", \"Ekurhuleni\", \"eThekwini\"). [Required: non-empty valid value must be supplied]."New value: +"Target South African municipality for plan submission (e.g. \"City of Johannesburg\", \"Tshwane\", \"City of Cape Town\", \"Ekurhuleni\", \"eThekwini\")."
    • changedInput schema / properties / project_name / description
      Previous value: -"Name of the building or architectural project. [Optional: omit to use server default filter]."New value: +"Name of the building or architectural project."
  3. Changed9 schema fields changed
    • changedInput schema / properties / external_wall_thickness_mm / description
      Previous value: -"External wall thickness in millimetres (standard cavity wall is min. 270 mm)."New value: +"External wall thickness in millimetres (standard cavity wall is min. 270 mm). [Optional: omit to use server default filter]."
    • changedInput schema / properties / gully_height_above_ground_mm / description
      Previous value: -"Height of sewer gully head coping above finished ground level in millimetres (min. 150 mm)."New value: +"Height of sewer gully head coping above finished ground level in millimetres (min. 150 mm). [Optional: omit to use server default filter]."
    • changedInput schema / properties / habitable_room_height_mm / description
      Previous value: -"Specified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm)."New value: +"Specified clear finished floor-to-ceiling height in habitable rooms in millimetres (min. 2,400 mm). [Optional: omit to use server default filter]."
    • changedInput schema / properties / has_rodding_eyes_at_bends / description
      Previous value: -"Whether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions."New value: +"Whether rodding eyes or inspection chambers are provided at drainage bends > 45° and junctions. [Optional: omit to use server default filter]."
    • changedInput schema / properties / has_sacap_declaration / description
      Previous value: -"Whether the drawing title block contains the registered architectural professional full name, registration number, category, and signature."New value: +"Whether the drawing title block contains the registered architectural professional full name, registration number, category, and signature. [Optional: omit to use server default filter]."
    • changedInput schema / properties / has_safety_glass_below_800mm / description
      Previous value: -"Whether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL."New value: +"Whether safety glass (SANS 1263-1) is specified for all glazing with sill < 800 mm from FFL. [Optional: omit to use server default filter]."
    • changedInput schema / properties / has_sans_forms / description
      Previous value: -"Whether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared."New value: +"Whether SANS 10400 Form 1 and Form 2 (if structural work included) are prepared. [Optional: omit to use server default filter]."
    • changedInput schema / properties / municipality / description
      Previous value: -"Target South African municipality for plan submission (e.g. \"City of Johannesburg\", \"Tshwane\", \"City of Cape Town\", \"Ekurhuleni\", \"eThekwini\")."New value: +"Target South African municipality for plan submission (e.g. \"City of Johannesburg\", \"Tshwane\", \"City of Cape Town\", \"Ekurhuleni\", \"eThekwini\"). [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / project_name / description
      Previous value: -"Name of the building or architectural project."New value: +"Name of the building or architectural project. [Optional: omit to use server default filter]."
  4. First observed

TDQS

B3.4/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, and it does disclose the return payload (readiness score, defect warnings, Stage 4 roadmap, submission checklist), which is genuinely useful. It says nothing about whether the operation is read-only, whether anything is persisted, permission or authentication needs, latency, or what a 'Stage 4 roadmap' actually contains. Adequate but with clear gaps for an unannotated tool.

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 action stated first and the outputs enumerated after; nothing is padded. It is dense enough that the four listed outputs run together, and splitting the return description into its own sentence would aid scanning, but there is no wasted wording.

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 12-parameter validation tool with no annotations and no output schema, the description does well to enumerate the return contents, which substitutes partly for a missing output schema. It still leaves unclear how the readiness score is scaled, whether defects are blocking, and whether calling it has any side effects. Enough to invoke correctly, not enough to interpret results confidently.

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 12 parameters including the building_class and submission_scope enums are already well documented in the schema. The description adds essentially no parameter-level meaning beyond echoing that it operates on plan or Concept Sketch specifications. Baseline 3 applies because the schema is doing the work.

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 gives a specific verb and object: 'Run an automated multi-point regulatory validation' on building plan or Concept Sketch specifications, and it names the concrete outputs. That is far more informative than the tool name alone. It does not explicitly distinguish itself from siblings such as check_municipal_requirements or get_sans_rules, so an agent must infer the boundary between a broad pre-check and the narrower calculators.

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 phrase 'compliance readiness score' and 'municipal submission checklist' suggest this is the pre-submission gatekeeper, and the 'Pre-Council Concept Sketch' mention hints at early-stage use. There is no explicit statement of when to choose this over check_municipal_requirements or the calculate_* siblings, and no exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources