Skip to main content
Glama

GetLawED — Verified South African Law

Check South African citations

legal_verify_citations
Read-onlyIdempotent

Check the South African case citations and Acts in a piece of text against GetLawED's library of official copies and verified records. Each item comes back as found, found_by_citation (a bare citation with no party names that resolves to a judgment we hold — parties were not compared, so confirm the name in the returned title), mismatch (the citation belongs to a different case), name_only, not_found, repealed or unchecked. "not_found"/"unchecked" means "check the law reports", not "fake".

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": {
      "text": "<text>"
    },
    "name": "legal_verify_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text containing citations (max 20 000 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/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), and the description goes well beyond them by enumerating every possible result status and explaining what each means in practice. The caveat that found_by_citation skipped party-name comparison and requires manual name confirmation is exactly the kind of hidden behavioral trait that changes how an agent interprets output.

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?

The purpose leads in the first sentence and the return semantics follow, so it is properly front-loaded with no filler. The status enumeration is dense but every token carries information an agent needs; only the slight run-on structure keeps it from a 5.

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

Completeness5/5

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

No output schema exists, so the description carries the burden of explaining returns — and it does so exhaustively via the status list. For a one-parameter, read-only, idempotent check with annotations covering safety, nothing an agent needs is missing apart from trivia already in the schema.

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 parameter at 100% schema coverage, and the schema already documents both the type and the 20,000-character limit. The description's "a piece of text" restates rather than extends that; baseline 3 applies when the schema carries the full parameter burden.

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?

Uses a specific verb ("check") and a precise resource ("South African case citations and Acts in a piece of text") against a named corpus (GetLawED's library of official copies). The purpose is unambiguous, but it never explicitly contrasts itself with the sibling tools legal_library_search or legal_get_section, so differentiation is left to inference from the noun phrase.

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 by the phrasing "in a piece of text" — it applies when you already have text containing citations — and the closing guidance ("'not_found'/'unchecked' means 'check the law reports', not 'fake'") tells the agent how to act on results. However, it never states when to prefer this over legal_library_search, nor any prerequisites or exclusions.

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.