Skip to main content
Glama

GetLawED — Verified South African Law

Find the municipality for a South African place

bylaws_find_municipality
Read-onlyIdempotent

Turn a South African town, suburb or municipality name (e.g. "Hermanus", "Centurion", "Mossel Bay") into its municipality, province and district, and list which municipal by-laws GetLawED holds for it by topic, whether its land use / zoning scheme and planning by-law are held, and the council's own by-law page. Start here for any question about local rules (building, boundary walls, second dwellings, home businesses, signage, keeping animals, water, refuse, trading). Does not hold the zoning of individual erven.

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": "bylaws_find_municipality"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesTown, suburb or municipality name, or a municipal code such as "WC043" or "CPT". Not a street address or erf number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description needn't restate safety. It does add genuine value by disclosing the source (GetLawED's holdings), enumerating what is returned (by-laws by topic, whether zoning scheme and planning by-law are held, the council's own page), and flagging one coverage limit (no individual erf zoning). It says nothing about behavior when a place is not found or ambiguous, which is the main remaining gap.

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?

Front-loaded with the core transformation, then coverage, then usage. The parenthetical topic list is long but each item is a real trigger for the tool, so it earns its space; the sentences are otherwise dense with little redundancy.

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?

With one fully specified parameter, no output schema and rich annotations, the description carries the return-shape burden well by enumerating the fields returned. Only a note on not-found or ambiguous-place behavior would make it complete for an agent calling it cold.

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% and the single 'place' parameter is already fully documented, including accepted municipal codes and the street-address/erf exclusion. The description only adds illustrative example values ("Hermanus", "Centurion", "Mossel Bay"), so the baseline 3 is appropriate.

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 concrete transformation (place name -> municipality, province, district) plus what it reports about by-law holdings and coverage. It is distinguishable as a resolver/entry point, though it never names its obvious siblings bylaws_for_place or zoning_scheme_for_place to sharpen 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 Guidelines4/5

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

Gives explicit when-to-use guidance ("Start here for any question about local rules") with a concrete topic list (building, boundary walls, second dwellings, home businesses, signage, animals, water, refuse, trading) and one clear exclusion ("Does not hold the zoning of individual erven"). What's missing is a named alternative for that excluded case, so the agent must guess which sibling to route to.

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.