Skip to main content
Glama

Prawnet: Polish case law and legislation

Szukaj w bibliotekach wiedzy Prawnet

szukaj_wiedzy
Read-onlyIdempotent

Wyszukiwanie w redakcyjnych bibliotekach Prawnet: wzory pism (115; metadane i link, bez treści wzoru), procedury krok po kroku (31), słownik pojęć prawnych (131 haseł), baza wiedzy — odpowiedzi na pytania prawne (315). fraza: słowa (odmiana dopasowywana po rdzeniu, trafienia w tytule ważą więcej) albo cytat przepisu (wtedy treści z tym artykułem w podstawie prawnej). Zwraca do 20 pozycji: typ, tytuł, kategoria, opis do 300 znaków, podstawa prawna, URL prawnet.pl; wzór — także czy to szkielet pisma procesowego. Dopasowanie leksykalne (słowa), nie semantyczne. Treści redakcyjne sprawdzone z tekstami ustaw; informacja ogólna, nie porada prawna.

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": {
      "fraza": "<fraza>"
    },
    "name": "szukaj_wiedzy"
  }
}

Input Schema

NameRequiredDescriptionDefault
typNoJedna biblioteka: wzor (wzory pism), procedura, haslo (słownik), pytanie (baza wiedzy); brak = wszystkie
frazaYesSłowa kluczowe ("wypowiedzenie najmu") albo cytat przepisu ("art. 445 k.c."). Do 200 znaków
jezykNopl (domyślnie) albo en (te same treści po angielsku; przepisy w polskiej formie cytatu)
limitNoDomyślnie 8

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, and the description layers on genuinely non-obvious traits: results capped at 20, matching is lexical not semantic, "wzor" returns metadata and a link but not the template body, editorial content is verified against statutes, and output is general information rather than legal advice.

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?

Front-loaded with scope and library counts, then query modes, then return shape — logical order with no filler sentences. It is dense and somewhat long, and the return-field enumeration partly duplicates the existing output schema.

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?

For a four-parameter search tool with an output schema and full annotation coverage, nothing needed to call it correctly is missing: scope, query syntax, match semantics, result cap, and the caveat about template bodies are all stated.

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 baseline is 3; the description still adds value by explaining that "fraza" accepts either keywords (with stem-based inflection matching and heavier weight on title hits) or a statutory citation that matches on podstawa prawna. The "wzor"-only extra return (whether it is a procedural pleading skeleton) is also flagged, though limits/language details stay in the schema.

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?

Names a specific verb and resource ("Wyszukiwanie w redakcyjnych bibliotekach Prawnet") and enumerates the four libraries with item counts (115 wzorów, 31 procedur, 131 haseł, 315 pytań). That inventory implicitly separates it from sibling searches like szukaj_aktow and szukaj_orzeczen without opening their schemas.

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?

Gives clear context for the two query modes: keywords with stem matching, or a statute citation when you want content grounded in a specific article. It does not explicitly name an alternative tool or state when not to use it, so it stops short of the 5 bar.

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