Skip to main content
Glama

GetLawED — Verified South African Law

Find a law firm

find_law_firms
Read-onlyIdempotent

Find South African law firms (on GetLawED) that accept consultation bookings from AI assistants. Filter by practice area and/or city/province. Returns each firm's id to use with the other tools.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity or town, e.g. "Cape Town", "Gqeberha" (old names such as Port Elizabeth also work)
provinceNoProvince, e.g. "Gauteng"
practice_areaNoArea of law the person needs help with

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds domain context the annotations cannot: the catalogue is South African firms on GetLawED, restricted to those accepting AI-assistant bookings, and it discloses the return shape (firm id) needed for subsequent calls.

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 short sentences, front-loaded with the resource and its scope, then the filter axes, then the return value. Nothing is redundant or padded.

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 read-only, zero-required-parameter search with full schema coverage and no output schema, the description covers scope, filters and return value adequately. It leaves out result limits/pagination and whether matches are matched per-firm on multiple practice areas, which would help an agent interpret thin result sets.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so city, province and practice_area are already documented with examples and an enum. The description still adds combining semantics with "and/or", telling the agent the filters may be used together or singly, which the schema alone does not spell out.

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?

The description names a specific verb and resource ("Find South African law firms") and scopes it precisely: GetLawED directory members that accept consultation bookings from AI assistants. It also signals its role as the entry point by stating it returns the firm id used with the other tools, which separates it from get_firm.

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?

It clearly frames usage: filter by practice area and/or city/province, with all filters optional, and it points forward to the other tools via the returned id. It stops short of explicitly saying when to use get_firm or check_availability instead, so the routing guidance is implied rather than stated.

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.