Skip to main content
Glama

GetLawED — Verified South African Law

What the by-laws say on a subject in a South African place

bylaw_rules_for
Read-onlyIdempotent

Find the sections of a South African municipality's by-laws and zoning scheme on one subject — e.g. "boundary wall height", "second dwelling", "home business", "keeping chickens", "building line", "signage", "noise" — and quote their wording with the by-law title, section number, status and official link. Read a whole section with legal_get_section (doc_id + section). Repealed by-laws are left out.

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>",
      "subject": "<subject>"
    },
    "name": "bylaw_rules_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum sections, 1-10 (default 5)
placeYesTown, suburb or municipality name, or a municipal code (e.g. "WC043")
topicNoOptional: search only by-laws of this topic
subjectYesThe subject in a few plain words (e.g. "boundary wall height")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are verbatim quotations carrying bylaw title, section number, status and official link, and repealed instruments are filtered out. It does not describe ranking or what happens when nothing matches.

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 verb and scope, followed by the hand-off to legal_get_section and the repeal caveat — no filler sentences. The inline list of example subjects is long but each example earns its place by anchoring vague queries like "home business" or "noise".

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 carries the burden of describing returns and does so reasonably (quoted wording plus title, section, status, link). For a search tool over a legal corpus, missing details are minor: no note on ordering, empty-result behavior, or how far the official link takes the agent.

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%, so all four parameters are already documented, including the limit range and the topic enum. The description adds only illustrative subject phrasing ("boundary wall height", "keeping chickens") and implies the place is a municipality; it says nothing extra about topic or limit semantics. 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?

States a specific verb and resource — find by-law and zoning-scheme sections for a subject in a named South African municipality — plus the return content (quoted wording, title, section number, status, official link). It also signals the boundary against the sibling legal_get_section, which reads a whole section rather than searching by subject.

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?

Explicitly routes the agent onward: "Read a whole section with legal_get_section (doc_id + section)", and gives concrete subject examples that match realistic queries. It also states the exclusion rule that repealed by-laws are omitted. It stops short of saying when to prefer bylaws_for_place or zoning_scheme_for_place over this subject-based search.

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.