Skip to main content
Glama

SA Build & Renovation Costs

Estimate cost of building a new house or extension

estimate_new_build
Read-only

Estimates the construction cost of a new house or extension in South Africa from floor area, quality level and region, using rand-per-m² rates. Optionally adds professional fees and municipal plan fees as a percentage.

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": {
      "floor_area_m2": "<floor_area_m2>"
    },
    "name": "estimate_new_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoRegion id: cape-town, cape-winelands, west-coast, overberg, garden-route, johannesburg, pretoria, durban, gqeberha, bloemfontein or rural. Default cape-towncape-town
qualityNoFinish quality: economy, standard or premium. Default standardstandard
include_vatNoAdd 15% VAT to the total. Default true
double_storeyNoTrue for a double-storey build (adds about 8% to the rate). Default false
floor_area_m2YesGross floor area to build, in m²
contingency_pctNoAllowance for unforeseen costs, as % of the works. Default 10
professional_fees_pctNoArchitect, engineer, etc. Default 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / contingency_pct / description
      Added value: +"Allowance for unforeseen costs, as % of the works. Default 10"
    • addedInput schema / properties / double_storey / description
      Added value: +"True for a double-storey build (adds about 8% to the rate). Default false"
    • addedInput schema / properties / floor_area_m2 / description
      Added value: +"Gross floor area to build, in m²"
    • addedInput schema / properties / include_vat / description
      Added value: +"Add 15% VAT to the total. Default true"
    • addedInput schema / properties / quality / description
      Added value: +"Finish quality: economy, standard or premium. Default standard"
    • addedInput schema / properties / region / description
      Added value: +"Region id: cape-town, cape-winelands, west-coast, overberg, garden-route, johannesburg, pretoria, durban, gqeberha, bloemfontein or rural. Default cape-town"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, closed-world), so the description's contribution is the pricing method — rand-per-m² regional rates with quality tiers and optional percentage add-ons. That is genuinely useful context, but it never says what the response contains or how the add-ons are compounded, and it promises 'municipal plan fees as a percentage' when no such parameter exists in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose and followed by the optional modifiers. No filler, no repetition of the title, and the most decision-relevant information comes first.

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?

With no output schema, the description should indicate the shape of the result — whether a single total, a works subtotal, a fees line and VAT are returned separately — and it does not. For a financial estimation tool where the agent may need to quote figures onward, that is a material omission.

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 coverage is 100%, so every parameter is already documented, and the description only restates that area, quality and region drive the rate while fees are percentages. It adds no format or interaction detail beyond the schema, and the mention of municipal plan fees does not map to any actual parameter.

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 (estimates) and resource (construction cost of a new house or extension) plus geography (South Africa) and the three driving inputs. It does not explicitly distinguish itself from the sibling estimate_works, which appears to be a closely related cost tool, so an agent still has to guess at the boundary.

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 implied by the scope phrase 'new house or extension', which suggests a new-build rather than renovation scenario, but there is no explicit when-to-use instruction, no exclusions, and no pointer to estimate_works or renovation_flip_check as alternatives. The agent must infer routing from the tool name.

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