Skip to main content
Glama

Prawnet: Polish case law and legislation

Właściwy sąd dla miejscowości

wlasciwy_sad
Read-onlyIdempotent

Sąd rejonowy, okręgowy i apelacyjny, którego obszar właściwości obejmuje miejscowość, gminę lub dzielnicę — według rozporządzenia Ministra Sprawiedliwości w sprawie siedzib i obszarów właściwości sądów (Dz.U. 2018 poz. 2548, tekst jednolity Dz.U. 2026 poz. 492) i TERYT GUS (gminy, miejscowości). Wynik: nazwy i siedziby sądów, zakres spraw sądu rejonowego z rozporządzenia, sądy okręgu rozpoznające sprawy spoza tego zakresu, zapowiedziane zmiany obszaru z datą, podstawa prawna. Miasto podzielone między sądy (np. Warszawa, Kraków, Łódź, Wrocław, Poznań, Gdańsk): status kilka_sadow z opisem części miasta. Nazwa niejednoznaczna lub nieznana: status z kandydatami.

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": {
      "miejscowosc": "<miejscowosc>"
    },
    "name": "wlasciwy_sad"
  }
}

Input Schema

NameRequiredDescriptionDefault
gminaNoGmina (rozróżnia miejscowości o tej samej nazwie)
powiatNoPowiat, np. "tatrzański"
dzielnicaNoDzielnica lub osiedle w mieście podzielonym między sądy, np. "Nowa Huta"
miejscowoscYesMiejscowość, gmina, miasto lub dzielnica, np. "Zakopane", "Mokotów"
wojewodztwoNoWojewództwo, np. "małopolskie"

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world lookup, so the bar is lower. The description goes further by naming the authoritative sources (the Minister of Justice regulation with journal citations and GUS TERYT data) and by disclosing the distinct outcome states — 'kilka_sadow' with a description of city parts, and a candidate list for ambiguous or unknown names — which an agent could not infer from annotations alone.

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?

Roughly four sentences, each carrying content: jurisdiction scope, result contents, split-city status, and ambiguity status. The long first sentence with full journal citations is heavy but front-loads the core answer, and the legal citation supports trust in the output rather than being filler.

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

Completeness3/5

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

There is an output schema, so the detailed enumeration of return fields is partly redundant, and the description omits the practical consequences of an ambiguous result, such as whether the caller should retry with gmina or powiat. It covers the tool's domain complexity and edge cases well but does not tell the agent how to proceed from a candidate-list response.

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%, so every parameter is already documented, including the disambiguation role of gmina, powiat and wojewodztwo. The description reinforces the dzielnica case by explaining that split cities require a district, but it adds little beyond what the schema already states, so the baseline of 3 applies.

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?

The description precisely identifies the resource — the regional, district and appellate court whose jurisdiction covers a given locality — and enumerates what the result contains (court names and seats, case scope, announced changes, legal basis). No sibling tool overlaps this function, so no differentiation is needed, though it is framed as a noun phrase rather than an explicit 'returns X for Y' verb statement.

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 this when you need the competent court for a place, gmina or district. It adds useful input-interpretation rules (a gmina disambiguates same-named localities; a district is needed for cities split between courts) and describes what happens on ambiguous or unknown names, but it never states when NOT to use it or which sibling to prefer for adjacent legal questions.

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.

Resources