Skip to main content
Glama

Cash-service.pl

Komornik sądowy (po nazwisku albo adresie dłużnika)

komornik
Read-onlyIdempotent

Wyszukiwarka komorników sądowych: po nazwisku (opcjonalnie miasto) zwraca kancelarię z adresem, telefonem, rachunkiem i sądem rejonowym; po adresie dłużnika (miejscowość, ulica, numer albo kod) - komorników właściwych dla rewiru danego sądu rejonowego.

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

Input Schema

NameRequiredDescriptionDefault
nrNoNumer budynku (opcjonalnie, gdy ulica jest dzielona między rewiry)
kodNoKod pocztowy 00-000
ulicaNoNazwa ulicy bez numeru (opcjonalnie, zawęża wynik w dużych miastach)
miastoNoMiasto kancelarii (z nazwiskiem)
nazwiskoNoNazwisko komornika
miejscowoscNoMiejscowość dłużnika (tryb po adresie)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 by structured data. The description adds value by disclosing the return payload (kancelaria with address, phone, bank account and district court) — necessary since there is no output schema. However, it says nothing about behavior with an empty call or mixed-mode parameters, a real gap given zero required parameters.

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 two parallel clauses mirroring the two search modes; every clause carries information about queries or results. The dense semicolon construction in Polish is readable but packs three result fields into one run-on segment.

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?

No output schema exists, and the description compensates by enumerating the returned office fields and the jurisdictional logic of the address mode. Still, for a six-parameter, zero-required-parameter tool it omits what happens when the query is empty or ambiguous, and offers no pointer to sibling tools like sad_wlasciwy for court determination.

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 each of the six parameters is already documented, including hints like '(tryb po adresie)'. The description reinforces the mode grouping and clarifies that the address mode resolves jurisdiction ('komorników właściwych dla rewiru danego sądu rejonowego'), which is meaningful context. It does not explain edge cases such as combining nazwisko with miejscowosc or why nr matters only for split streets beyond what the schema 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?

Names a specific resource (komornicy sądowi) and a specific lookup action, and distinguishes two search modes (by surname vs. by debtor address) that yield different result sets. It does not explicitly contrast with the closest sibling, sad_wlasciwy, but the dual-mode framing makes the tool's identity unambiguous.

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?

The description tells the agent which parameter combinations go with which mode: 'po nazwisku (opcjonalnie miasto)' vs. 'po adresie dłużnika (miejscowość, ulica, numer albo kod)'. That is real routing guidance between the two usage patterns. It stops short of stating when to prefer this tool over siblings or what to do when no parameters are supplied.

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