Skip to main content
Glama

SA Build & Renovation Costs

Estimate cost of building or renovation work

estimate_works
Read-only

Prices a list of building/renovation items (by code from list_cost_items, with quantities) for a South African region and quality level. Returns material and labour per line, preliminaries, contingency, VAT, total and a likely range in rand.

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": {
      "items": "<items>"
    },
    "name": "estimate_works"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesItems to price, each an item code and a quantity
regionNoRegion id: cape-town, cape-winelands, west-coast, overberg, garden-route, johannesburg, pretoria, durban, gqeberha, bloemfontein or rural. Default cape-town
qualityNoFinish quality: economy, standard or premium. Default standardstandard
include_vatNoAdd 15% VAT to the total. Default true
contingency_pctNoAllowance for unforeseen costs, as % of the works. Default 10
preliminaries_pctNoSite setup, supervision, rubble etc. Default 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / contingency_pct / description
      Added value: +"Allowance for unforeseen costs, as % of the works. Default 10"
    • addedInput schema / properties / include_vat / description
      Added value: +"Add 15% VAT to the total. Default true"
    • addedInput schema / properties / items / description
      Added value: +"Items to price, each an item code and a quantity"
    • addedInput schema / properties / items / items / properties / code / description
      Added value: +"Item code from list_cost_items, e.g. ROOF-IBR"
    • addedInput schema / properties / items / items / properties / quantity / description
      Added value: +"Quantity in the item's unit (m², m, each, etc.)"
    • addedInput schema / properties / quality / description
      Added value: +"Finish quality: economy, standard or premium. Default standard"
    • changedInput schema / properties / region / description
      Previous value: -"Region id, default cape-town"New 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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value by enumerating the returned breakdown (material and labour per line, preliminaries, contingency, VAT, total, and a likely range in rand) and by disclosing that VAT is 15%. It does not mention currency rounding rules or behaviour for unknown item codes, which would have made it a 5.

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 dense sentences with no filler, front-loading the input contract before the return shape. Every clause carries information an agent would otherwise have to infer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter pricing tool with no output schema, the description covers the input contract, the prerequisite sibling for codes, and the full shape of the result, including the currency and the range estimate. Nothing essential to a correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining that region is a South African locale, that quality drives pricing, and how contingency/preliminaries/VAT feed the returned total. The per-parameter meaning of contingency_pct and preliminaries_pct is still left mostly to the schema.

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 (prices) and resource (a list of building/renovation items) and ties the input to the sibling tool list_cost_items for item codes. It is clearly distinguishable from a configure-a-build tool, though it never explicitly contrasts itself with estimate_new_build or roof_replacement_estimate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for use: supply codes from list_cost_items with quantities, for a South African region and a quality level. It stops short of stating when to prefer estimate_new_build or roof_replacement_estimate instead, and lists no exclusions.

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