Skip to main content
Glama
numikel

Law Scrapper MCP

by numikel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Powiązania aktu prawnego

analyze_act_relationships
Read-onlyIdempotent

Analyze legal act relationships to identify amended, amending, and repealed acts, legal bases, and consolidated texts. Filter by relationship type for precise results.

Instructions

Przeanalizuj powiązania i referencje między aktami prawnymi.

Zwraca informacje o aktach zmienionych, zmieniających, uchylonych, podstawie prawnej i tekstach jednolitych.

Przykłady:

  • analyze_act_relationships(eli="DU/2024/1716") - Wszystkie powiązania

  • analyze_act_relationships(eli="DU/2024/1716", relationship_type="Akty zmienione") - Jakie akty zmienił

  • analyze_act_relationships(eli="DU/2024/1716", relationship_type="Podstawa prawna") - Na jakiej podstawie powstał

  • analyze_act_relationships(eli="DU/2024/1716", relationship_type="Akty zmieniające") - Co go zmienia

  • analyze_act_relationships(eli="DU/2024/1", relationship_type="Akty uznane za uchylone") - Uchylone akty

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eliYesIdentyfikator ELI aktu. Format: "{wydawca}/{rok}/{pozycja}". Wydawcy: DU (Dziennik Ustaw), MP (Monitor Polski). Przykłady: "DU/2024/1716", "MP/2023/500", "DU/2024/1".
relationship_typeNoFiltruj po typie powiązania (dokładne dopasowanie do klucza z API). Dostępne typy: 'Akty zmienione', 'Akty zmieniające', 'Akty uchylone', 'Akty uchylające', 'Akty uznane za uchylone', 'Podstawa prawna', 'Podstawa prawna z art.', 'Teksty jednolite'. None = zwróć wszystkie powiązania.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe actual response data
hintsNoSuggested next steps

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.4.0
    • removedOutput schema / properties / metadata
      Removed value: -{
-  "additionalProperties": true,
-  "description": "Additional metadata",
-  "title": "Metadata",
-  "type": "object"
-}
  2. Changed11 schema fields changedv3.1.0
    • addedInput schema / properties / eli / title
      Added value: +"Eli"
    • addedInput schema / properties / relationship_type / title
      Added value: +"Relationship Type"
    • addedInput schema / title
      Added value: +"analyze_act_relationshipsArguments"
    • addedOutput schema / $defs
      Added value: +{
+  "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"
+  },
+  "RelationshipsOutput": {
+    "description": "Output for act relationships.",
+    "properties": {
+      "eli": {
+        "title": "Eli",
+        "type": "string"
+      },
+      "relationship_type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Relationship Type"
+      },
+      "relationships": {
+        "additionalProperties": true,
+        "title": "Relationships",
+        "type": "object"
+      },
+      "total_count": {
+        "title": "Total Count",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "eli",
+      "relationships",
+      "total_count"
+    ],
+    "title": "RelationshipsOutput",
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / data
      Added value: +{
+  "$ref": "#/$defs/RelationshipsOutput",
+  "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[RelationshipsOutput]"
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  3. Addedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only that the tool returns information about relationship categories; it does not disclose additional behavioral traits such as result completeness, pagination, or exact-match limitations, though the openWorldHint is present in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose, followed by a compact list of return categories and then five single-line examples. There is no filler; each example earns its place by illustrating a different relationship type.

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?

With an output schema present, return values do not need to be explained in the description. Both parameters are fully covered by the schema, annotations cover the read-only/idempotent behavior, and the examples complete the picture for selecting and invoking the tool correctly.

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 the parameters are already documented. The description adds value by mapping example relationship_type values to natural-language questions ('Jakie akty zmienił', 'Na jakiej podstawie powstał'), which clarifies the intended meaning beyond the raw key list.

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 clearly identifies the operation ('Przeanalizuj powiązania i referencje między aktami prawnymi') and enumerates the relationship categories returned, so an agent can tell it is about act-to-act references rather than document contents or search. It does not explicitly name or contrast sibling tools, which keeps it from a 5.

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?

The examples provide concrete call patterns for common needs (what an act amended, its legal basis, what amends it, repealed acts), giving clear context for when this tool answers relationship queries. It does not explicitly state when not to use it or direct the agent to an alternative sibling, but the intended use is strongly implied.

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