Skip to main content
Glama

SA Property Costs

Estimate monthly municipal property rates

municipal_rates
Read-only

Estimates municipal property rates on a South African property from its municipal valuation. Either pick a municipality from the built-in tariff list, or pass the cent-in-the-rand rate and rebate yourself. Call with list_municipalities=true to see which municipalities are covered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "municipal_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoRating category: residential, business, agricultural or vacant land. Default residentialresidential
municipalityNoMunicipality id from the tariff list, e.g. cape-town
rate_in_randNoOverride: annual rate per rand of value, e.g. 0.006428
list_municipalitiesNoTrue to return the list of covered municipalities and their ids instead of a calculation. Default false
municipal_valuationNoThe property's municipal valuation in rand (from the valuation roll), not the market price
valuation_exclusionNoOverride: rand amount of value exempt from rates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Rating category: residential, business, agricultural or vacant land. Default residential"
    • addedInput schema / properties / list_municipalities / description
      Added value: +"True to return the list of covered municipalities and their ids instead of a calculation. Default false"
    • addedInput schema / properties / municipal_valuation / description
      Added value: +"The property's municipal valuation in rand (from the valuation roll), not the market price"
  2. First observed

TDQS

A4.1/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 genuinely useful behavior beyond that: a built-in tariff list exists, overrides are permitted, and list_municipalities switches the tool from calculation to enumeration — a materially different return mode. It stops short of noting that results are estimates with no accuracy caveat or output shape.

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?

Three tight sentences, front-loaded with the purpose, then the two input paths, then the discovery hint. No redundant restatement of the name or title.

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 six parameters, zero required, and no output schema, the description leaves two gaps: it never says which inputs are minimally needed (valuation plus either municipality or rate) and never characterizes the returned estimate. For a calculation tool with no output schema, that is a meaningful omission, though the core usage is covered.

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 the schema already documents all six parameters, including the municipal-valuation-vs-market-price distinction. The description adds only light framing by mapping 'cent-in-the-rand rate and rebate' onto rate_in_rand and valuation_exclusion, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Estimates') and resource ('municipal property rates') with a clear scope: a South African property, derived from its municipal valuation. This is plainly distinguishable from the sibling tools (bond_repayment, purchase_costs, transfer_duty), which cover different cost components.

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 explicit operating modes: either select a municipality from the built-in tariff list or supply the cent-in-the-rand rate and rebate yourself, and points to list_municipalities=true to discover coverage. It does not state when to prefer this over siblings or what to do if the municipality is not covered, but the context is otherwise clear.

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