Skip to main content
Glama

Prawnet: Polish case law and legislation

Dyrektywy UE wdrażane przez akt

zrodla_ue_aktu
Read-onlyIdempotent

Akty UE (głównie dyrektywy), które wdraża polska ustawa lub rozporządzenie z Dz.U., według krajowych środków wykonawczych notyfikowanych przez Polskę Komisji Europejskiej (EUR-Lex / CELLAR): CELEX, oznaczenie, tytuł, termin transpozycji, czy w mocy, link EUR-Lex i notyfikowane środki. Tekst jednolity jest łączony z aktem bazowym. Tylko środki notyfikowane Komisji. Źródło: EUR-Lex.

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": {
      "y": "<y>",
      "p": "<p>"
    },
    "name": "zrodla_ue_aktu"
  }
}

Input Schema

NameRequiredDescriptionDefault
pYesPozycja w Dz.U. (nie numer)
yYesRok Dz.U.

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavior, so the description is not required to restate safety. It adds genuine context beyond the annotations: data flows from EUR-Lex/CELLAR, only measures notified by Poland to the Commission are returned, and consolidated texts are merged with the base act — all of which shape how results should be interpreted.

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 dense paragraph front-loaded with the core definition, followed by returned fields, scope caveats and source. Every clause carries information, though the final 'Źródło: EUR-Lex' partly repeats the earlier '(EUR-Lex / CELLAR)' mention.

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?

With an output schema present and full parameter descriptions, the description's job is to explain the data's origin and semantics, which it does: source registry, notification filter, and consolidation behavior. Minor gaps remain around behavior when the act has no notified measures or is not a Dz.U. act, but the definition is adequate for correct invocation.

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% and both parameters carry their own descriptions (year range for Dz.U., position not number), so the baseline is 3. The description situates the parameters in the Dz.U. context but adds no syntax or format detail beyond the schema.

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 states a specific resource and relationship: EU acts (mainly directives) transposed by a Polish statute or regulation identified by its Dz.U. year and position, plus the fields returned (CELEX, title, transposition deadline, in-force status, EUR-Lex link, notified measures). It is clearly distinct from siblings like szukaj_aktow or informacja_o_akcie, but it never names an alternative to contrast against, so 4 rather than 5.

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: given a Dz.U. year/position, use this to obtain the transposing EU directives. A meaningful scope restriction is stated ('Tylko środki notyfikowane Komisji'), but there is no explicit when-to-use/when-not guidance and no routing to sibling tools when the act is not in Dz.U. or when consolidated vs. base text matters.

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