Skip to main content
Glama

GetLawED — Verified South African Law

Zoning scheme for a South African place

zoning_scheme_for_place
Read-onlyIdempotent

The land use / zoning scheme (zoning scheme regulations) and the municipal planning by-law that apply in a South African place, with dates, gazette references, official links and doc_ids. These set what each zone allows (coverage, height, building lines, parking, consent uses) and how to apply for rezoning or departures. It does NOT say how a particular erf is zoned — that is on the municipality's zoning map or zoning certificate.

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": {
      "place": "<place>"
    },
    "name": "zoning_scheme_for_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesTown, suburb or municipality name, or a municipal code (e.g. "WC043")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit beyond that by disclosing the payload's nature — dated gazette references, official links and doc_ids — and by scoping the answer to the scheme rather than a parcel-level determination, which sets expectations about what a result can and cannot answer. It does not discuss coverage gaps, multiple schemes per place, or how to use the returned doc_ids.

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 sentences, front-loaded with the definition, then the practical content, then the negative scope. Every clause carries information an agent needs; there is no restatement of the title or filler.

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

Completeness4/5

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

For a single-parameter, read-only lookup with no output schema, the definition supplies enough: what the result contains, what it governs, and what it will not answer. The remaining gap is operational — whether one place can match multiple schemes, and how the returned doc_ids feed other tools — but nothing required to invoke it correctly is missing.

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?

There is a single required parameter with 100% schema description coverage; the schema already defines 'place' as a town, suburb, municipality name or municipal code such as "WC043". The description adds no format, normalization, or ambiguous-name behaviour beyond that, so the schema is doing all the parameter work and baseline 3 applies.

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?

Names a specific resource (zoning scheme regulations plus the municipal planning by-law) scoped to a South African place, and enumerates the fields returned (dates, gazette references, official links, doc_ids). It also states plainly what the tool does NOT return — how a particular erf is zoned — which separates it from a zoning-map or zoning-certificate lookup.

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?

The description gives a clear condition for use (you want the scheme regulations and by-law governing a place, including zone rules for coverage, height, building lines, parking and consent uses) and an explicit exclusion pointing elsewhere (municipality's zoning map or zoning certificate for a specific erf). It stops short of naming or contrasting a sibling tool, so routing between this and the bylaw tools is left to inference.

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.