Law Scrapper MCP

Overview Schema Source Related Servers Discussions Admin

Porównanie dwóch aktów

compare_acts

Read-onlyIdempotent

Compare metadata of two Polish legal acts to spot differences and shared elements across titles, types, statuses, dates, and keywords. Works without loading full content.

Instructions

Porównaj metadane dwóch aktów prawnych.

Porównuje tytuły, typy, statusy, daty (ogłoszenia, promulgacji, wejścia w życie), słowa kluczowe dwóch aktów. Identyfikuje różnice i wspólne elementy. Nie wymaga wcześniejszego załadowania treści (load_content).

Kiedy użyć: Aby porównać metadane dwóch aktów (np. wersji, powiązanych aktów). Kiedy NIE używać: Do porównania treści → załaduj oba akty i użyj read_act_content.

Przykłady:

compare_acts(eli_a="DU/2024/1692", eli_b="DU/2024/1716") - Porównaj dwa akty z 2024
compare_acts(eli_a="DU/2020/1444", eli_b="DU/2024/1692") - Porównaj starą i nową wersję
compare_acts(eli_a="DU/2024/1", eli_b="DU/2023/2000") - Porównaj akty z różnych lat
compare_acts(eli_a="DU/2024/100", eli_b="MP/2024/200") - Porównaj DU vs MP
compare_acts(eli_a="DU/2021/1500", eli_b="DU/2021/1600") - Porównaj podobne akty

Input Schema

TableJSON Schema

Name	Required	Description	Default
`eli_a`	Yes	Identyfikator ELI pierwszego aktu. Format: "{wydawca}/{rok}/{pozycja}". Przykłady: "DU/2024/1716", "MP/2023/500".
`eli_b`	Yes	Identyfikator ELI drugiego aktu do porównania. Format: "{wydawca}/{rok}/{pozycja}". Przykłady: "DU/2024/1692", "DU/2020/1444".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	The actual response data
`hints`	No	Suggested next steps

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv4.4.0Sep 15, 2026

removedOutput schema / properties / metadata

Removed value: -{
-  "additionalProperties": true,
-  "description": "Additional metadata",
-  "title": "Metadata",
-  "type": "object"
-}

Changed11 schema fields changedv3.1.0Aug 22, 2026

addedInput schema / properties / eli_a / title
```
Added value: +"Eli A"
```
addedInput schema / properties / eli_b / title
```
Added value: +"Eli B"
```
addedInput schema / title
```
Added value: +"compare_actsArguments"
```

addedOutput schema / $defs

Added value: +{
+  "CompareOutput": {
+    "description": "Output for comparing two acts.",
+    "properties": {
+      "common_keywords": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Common Keywords",
+        "type": "array"
+      },
+      "comparison": {
+        "additionalProperties": true,
+        "title": "Comparison",
+        "type": "object"
+      },
+      "differences": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Differences",
+        "type": "array"
+      },
+      "eli_a": {
+        "title": "Eli A",
+        "type": "string"
+      },
+      "eli_b": {
+        "title": "Eli B",
+        "type": "string"
+      }
+    },
+    "required": [
+      "eli_a",
+      "eli_b",
+      "comparison",
+      "common_keywords",
+      "differences"
+    ],
+    "title": "CompareOutput",
+    "type": "object"
+  },
+  "Hint": {
+    "description": "Hint for next actions or related tools.",
+    "properties": {
+      "message": {
+        "description": "Hint message",
+        "title": "Message",
+        "type": "string"
+      },
+      "parameters": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Suggested parameters",
+        "title": "Parameters"
+      },
+      "tool": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Related tool name",
+        "title": "Tool"
+      }
+    },
+    "required": [
+      "message"
+    ],
+    "title": "Hint",
+    "type": "object"
+  }
+}

addedOutput schema / properties / data

Added value: +{
+  "$ref": "#/$defs/CompareOutput",
+  "description": "The actual response data"
+}

addedOutput schema / properties / hints

Added value: +{
+  "description": "Suggested next steps",
+  "items": {
+    "$ref": "#/$defs/Hint"
+  },
+  "title": "Hints",
+  "type": "array"
+}

addedOutput schema / properties / metadata

Added value: +{
+  "additionalProperties": true,
+  "description": "Additional metadata",
+  "title": "Metadata",
+  "type": "object"
+}

removedOutput schema / properties / result

Removed value: -{
-  "type": "string"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "data"
+]

addedOutput schema / title

Added value: +"EnrichedResponse[CompareOutput]"

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

Addedv1.0.2Apr 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive hints. The description adds meaningful behavioral context by stating that no prior load_content is required and that the tool identifies differences and common elements. No contradiction with annotations.

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?

The description is well-organized with a purpose statement, details, usage rules, and examples. It is front-loaded and efficient, though the five examples are somewhat repetitive; each adds a slight variant but could be trimmed.

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 two-parameter read-only comparison tool with full schema coverage, an output schema, and annotations, the description covers purpose, usage boundaries, and prerequisite behavior. Nothing needed to invoke it correctly is missing.

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?

The input schema covers 100% of parameters with format and examples, giving a baseline of 3. The description's examples add extra semantic context—e.g., comparing old and new versions, DU vs MP—thereby clarifying valid combinations and intended use of eli_a and eli_b.

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?

The description opens with a clear verb+resource: 'Porównaj metadane dwóch aktów prawnych' (compare metadata of two legal acts) and enumerates the exact fields compared (titles, types, statuses, dates, keywords). It also explicitly distinguishes itself from content comparison by referring to read_act_content, so an agent can differentiate it from sibling tools.

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?

Contains explicit 'Kiedy użyć' (when to use) and 'Kiedy NIE używać' (when not to use) sections. It names read_act_content as the alternative for content comparison and describes the appropriate scenario (comparing versions/related acts), leaving no ambiguity.

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

Deploy Server