Skip to main content
Glama

GetLawED — Verified South African Law

List the by-laws of a South African municipality

bylaws_for_place
Read-onlyIdempotent

The municipal by-laws and land use schemes GetLawED holds for a South African place, optionally for one topic — each with its status (in force / amended / repealed), promulgation date, gazette reference, official source link and doc_id for legal_get_section. Repealed by-laws are left out unless asked for.

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_for_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesTown, suburb or municipality name, or a municipal code (e.g. "WC043")
topicNoOnly one topic: planning (land use, zoning, rezoning), building (building, signage, fencing), finance (rates, tariffs, credit control), utilities (water, sanitation, electricity), waste, roads_traffic, public_spaces (amenities, nuisances, noise), business (trading, liquor, guest houses), health_environment, animals, safety (fire, events, land invasion), governance, other
include_repealedNoAlso list repealed by-laws (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does: it discloses the default exclusion of repealed by-laws and enumerates the per-record fields returned (status, promulgation date, gazette reference, official source link, doc_id). It stops short of describing result volume, ordering, or error behavior for unmatched places.

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?

A single front-loaded sentence with an em-dash clause and a short follow-up; almost every element carries information. The field enumeration is slightly list-heavy but justified because no output schema exists, so the return shape has to be stated somewhere.

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 no output schema, the description correctly takes on the burden of describing the returned fields and the default filter, which is the main thing an agent needs before calling. Missing only secondary details such as result limits, ordering, and the boundary against zoning_scheme_for_place for land use schemes.

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%, with the enum and the 'only one topic' constraint fully documented there, so the baseline is 3. The description reinforces the single-topic limit and the repealed-by-default behavior, but adds no format hints (e.g. how municipal codes differ from town names) beyond what the schema already says.

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-and-resource pair: returns the by-laws and land use schemes GetLawED holds for a South African place, with an optional topic filter. The scope is clear and the mention of doc_id as a handoff to legal_get_section helps orient the agent, but it never distinguishes itself from the sibling zoning_scheme_for_place even though 'land use schemes' overlaps with that tool's likely territory.

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: call it with a place, optionally narrow by topic, and ask for repealed items only if wanted. There is a useful downstream pointer (doc_id feeds legal_get_section), but no explicit when-to-use versus bylaws_find_municipality, zoning_scheme_for_place, or bylaw_rules_for, and no guidance on what to do if the place name is ambiguous.

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.