Skip to main content
Glama

Prawnet: Polish case law and legislation

Przepisy powoływane razem

przepisy_powiazane
Read-onlyIdempotent

Artykuły najczęściej powoływane w tych samych orzeczeniach co dany artykuł (współcytowanie w grafie przepis → orzeczenie Prawnet). Dla każdego: n_razem (liczba wspólnych orzeczeń), udzial_pct (część orzeczeń badanego artykułu), lift (ile razy częściej niż przy cytowaniu niezależnym), pmi = log2(lift), URL strony przepisu, a dla par z ≥ 100 wspólnymi orzeczeniami — strona pary i 1–2 najnowsze wspólne orzeczenia (sygnatura, sąd, data, URL). Tabela par: n_razem ≥ 20, lift ≥ 1,5, bez przepisów cytowanych rutynowo (np. art. 98 k.p.c.). Ranking wg lift (domyślnie) albo n_razem, z progiem min_razem. Statystyka bez AI; wspólne powołanie nie oznacza związku merytorycznego.

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

Input Schema

NameRequiredDescriptionDefault
pNoBez przepis: POZYCJA w Dz.U., nie numer (k.c. 1964/93)
yNoBez przepis: rok Dz.U.
artNoBez przepis: nr artykułu ("385-1" = 385¹), do 16 znaków
limitNoPowiązanych artykułów; domyślnie 10
sortujNolift (domyślnie) albo n_razem
przepisNoCytat ("art. 446 § 4 kc", "art. 5 ustawy o prawach konsumenta") albo potoczna nazwa ("zasiedzenie"); zamiast y, p, art. Do 160 znaków
min_razemNoMinimum wspólnych orzeczeń pary; domyślnie 50

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 cover read-only, idempotent, non-destructive and closed-world, but the description adds real behavioral content: pair-table filters (n_razem ≥ 20, lift ≥ 1.5), exclusion of routinely cited provisions such as art. 98 k.p.c., and the extra per-pair data only above 100 shared rulings. The closing caveat that co-citation does not imply substantive relation is exactly the kind of interpretive warning annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the text is information-dense rather than padded, but the long enumeration of return fields (n_razem, udzial_pct, lift, pmi, URL, pair page, newest rulings) duplicates what the output schema already provides. It reads as one unbroken block with no structural separation between output shape, filtering rules and caveats.

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 statistical graph tool with seven optional parameters, the definition covers methodology, filtering thresholds, default ranking and a crucial interpretation caveat, which is close to complete. The remaining gap is routing guidance relative to the many sibling tools, which the agent must infer.

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 the schema already documents p, y, art, przepis, limit, sortuj and min_razem, including the citation-vs-coordinate alternative. The description only reinforces the sortuj/min_razem defaults and relationship, adding little beyond the structured fields; baseline 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?

States a specific analytical operation on a specific resource: articles most often cited in the same rulings as a given article, via co-citation in the Prawnet provision→ruling graph. The co-citation framing inherently separates it from sibling tools like orzeczenia_do_przepisu or cytowania_orzeczenia, though no sibling is named explicitly.

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 methodology rather than stated: an agent can infer it is for finding provisions statistically associated with a given article. It gives useful selection detail (default ranking by lift, alternative by n_razem, min_razem threshold) but never says when to prefer it over a related tool or when it is the wrong choice.

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