Skip to main content
Glama
kamilkaczmareksolutions

Polish MCP Servers

by kamilkaczmareksolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Polish Statutes & Court Rulings MCP – Dziennik Ustaw, SAOS

polish-law-mcp-server
Read-onlyIdempotent

Searches and reads specific Polish legal acts, articles, and SAOS court judgments via live official ELI/SAOS APIs, returning text and metadata on demand.

Instructions

Makes one call to the Polish Law MCP Actor, which reads the official Sejm ELI API (Dziennik Ustaw, Monitor Polski) and the SAOS court judgments API live: set tool to search_legal_acts, get_legal_act, get_legal_act_text (current consolidated wording, optionally one article), list_changed_legal_acts, search_court_judgments or get_court_judgment, and pass that tool's arguments. Use it to find or read one specific act, article or judgment; for bulk filtered lists or onlyNew feeds use polish-legal-acts-eli or polish-court-judgments-saos. Read-only: it only queries the public sources and never writes to them. Each call needs the APIFY_TOKEN env var and starts one paid run of the Apify Actor enterprising_hamster/polish-law-mcp-server on your Apify account, billed pay-per-event per successful tool call (calls returning full text cost more; failed or empty calls are free) plus any Apify platform usage. The server waits up to 300 s; ELI answers in about a second, SAOS searches take 1-20 s and one full SAOS judgment 15-60 s.

Input Schema

NameRequiredDescriptionDefault
toolNoWhich law tool to run once. search_legal_acts: find acts by title stem, publisher (DU or MP), year, type, keywords, in-force status or date range. get_legal_act: metadata, status and references of one act. get_legal_act_text: plain text of an act or one article (newest consolidated text), paged. list_changed_legal_acts: acts whose ELI record changed since a time. search_court_judgments: find SAOS judgments. get_court_judgment: full text and metadata of one judgment.search_legal_acts
maxItemsNoMaximum dataset items returned to the client (1-100), applied by this server to the run's dataset.
argumentsNoArguments object for the chosen tool, exactly as the hosted Polish Law MCP server takes them, e.g. {"title": "ochron danych", "limit": 5} for search_legal_acts, {"eli": "DU/1964/93", "article": "415"} for get_legal_act_text (an ELI id or a Dz.U. citation), or {"query": "art. 415 k.c.", "court_type": "SUPREME", "limit": 5} for search_court_judgments. Full argument lists: https://apify.com/enterprising_hamster/polish-law-mcp-server

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / arguments / description
      Previous value: -"Arguments for the tool as a JSON object, exactly as an MCP client would send them. See the README for every tool's parameters."New value: +"Arguments object for the chosen tool, exactly as the hosted Polish Law MCP server takes them, e.g. {\"title\": \"ochron danych\", \"limit\": 5} for search_legal_acts, {\"eli\": \"DU/1964/93\", \"article\": \"415\"} for get_legal_act_text (an ELI id or a Dz.U. citation), or {\"query\": \"art. 415 k.c.\", \"court_type\": \"SUPREME\", \"limit\": 5} for search_court_judgments. Full argument lists: https://apify.com/enterprising_hamster/polish-law-mcp-server"
    • changedInput schema / properties / maxItems / description
      Previous value: -"Maximum dataset items returned to the client."New value: +"Maximum dataset items returned to the client (1-100), applied by this server to the run's dataset."
    • changedInput schema / properties / tool / description
      Previous value: -"The MCP tool to call once."New value: +"Which law tool to run once. search_legal_acts: find acts by title stem, publisher (DU or MP), year, type, keywords, in-force status or date range. get_legal_act: metadata, status and references of one act. get_legal_act_text: plain text of an act or one article (newest consolidated text), paged. list_changed_legal_acts: acts whose ELI record changed since a time. search_court_judgments: find SAOS judgments. get_court_judgment: full text and metadata of one judgment."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations by disclosing operational cost and timing: APIFY_TOKEN required, one paid Apify run per call, pay-per-event billing where full-text calls cost more and failed/empty calls are free, plus a 300 s wait ceiling with ELI ~1 s vs SAOS 1-60 s expectations. It does not describe the shape of the returned dataset items, which is the remaining gap for a delegating wrapper.

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-loads the core dispatch action, then tool list, then alternatives, then cost/latency in a single dense paragraph with no filler. The billing and timing clauses are long but each carries decision-relevant information; a bulleted split would read better than one flowing block.

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 3-parameter wrapper with no output schema, the description covers auth, billing, timeouts, latency per backend, read-only safety and sibling alternatives. It stops short of describing what the dataset result looks like or how errors surface, which would fully close the loop for a delegating tool.

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 routing value by explaining that `arguments` must match the hosted server's per-tool signature and by noting an ELI id may be given as a Dz.U. citation. Some example argument objects duplicate what the schema already shows, limiting the gain beyond baseline.

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?

States a specific verb and resource: one dispatch call to the Polish Law MCP Actor reading the Sejm ELI API and SAOS judgments API, enumerating the six sub-tools it can run. It also names the exact siblings (polish-legal-acts-eli, polish-court-judgments-saos) it is not, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule: "Use it to find or read one specific act, article or judgment" versus bulk filtered lists or onlyNew feeds which belong to the sibling Actors. The enum-level text in the description also spells out what each of the six tools does, removing ambiguity about which value to set.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools