Law Scrapper MCP

Overview Schema Source Related Servers Discussions Admin

Porównanie metadanych dwóch aktów

compare_acts

Read-onlyIdempotent

Compare metadata of two legal acts to identify differences and shared elements, including titles, types, statuses, dates, and keywords.

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

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

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.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description still adds genuine behavioral context: no prior load_content call is needed, and the comparison produces identified differences plus common elements. It does not discuss cost or output shape, but the output schema covers returns.

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?

Front-loaded with purpose and well-sectioned, but five examples all convey the same idea (a pair of ELI strings, including cross-year and cross-publisher). Three would have sufficed; the block adds bulk without new information.

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?

Covers purpose, comparison fields, the no-load prerequisite, and routing to the content-comparison path; annotations and an output schema handle safety and return values. Only gap is ordering/edge-case semantics of the ELI pair, which is minor for a read-only comparison tool.

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 ELI parameters are fully documented with format and examples, so the schema does the heavy lifting. The description's examples restate the same ELI format rather than adding new semantic constraints (e.g. whether order matters, whether same-act comparison is rejected).

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+resource ('Porównaj metadane dwóch aktów') and enumerates exactly what is compared (tytuły, typy, statusy, daty, słowa kluczowe). It explicitly separates itself from content comparison via read_act_content, so an agent can distinguish it from all siblings 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?

Contains explicit 'Kiedy użyć' and 'Kiedy NIE używać' sections, and the negative case names the exact alternative workflow (load both acts, then read_act_content). This is textbook when/when-not/alternative guidance.

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

Deploy Server