Law Scrapper MCP

Overview Schema Source Related Servers Discussions Admin

Metadane systemu ELI

get_system_metadata

Read-onlyIdempotent

Retrieve legal act metadata categories like keywords, publishers, types, statuses, and institutions to filter and refine legal searches.

Instructions

Pobierz metadane systemu aktów prawnych.

Zwraca dostępne słowa kluczowe, wydawców, typy dokumentów, statusy i instytucje, które można wykorzystać do filtrowania i wyszukiwania aktów prawnych.

Przykłady:

get_system_metadata(category="keywords") - Dostępne słowa kluczowe do wyszukiwania
get_system_metadata(category="types") - Typy dokumentów (Ustawa, Rozporządzenie itp.)
get_system_metadata(category="publishers") - Wydawcy (DU, MP)
get_system_metadata(category="statuses") - Statusy aktów (obowiązujący, uchylony itp.)
get_system_metadata(category="all") - Wszystkie kategorie metadanych

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maksymalna liczba wartości metadanych na stronie odpowiedzi (domyślnie 20, maks. 100).
`offset`	No	Nieujemne przesunięcie strony metadanych.
`category`	No	Kategoria metadanych: 'keywords' (słowa kluczowe do wyszukiwania), 'publishers' (wydawcy: DU, MP), 'statuses' (statusy aktów), 'types' (typy dokumentów: Ustawa, Rozporządzenie itp.), 'institutions' (instytucje wydające), 'all' (wszystkie kategorie). Domyślnie 'all'.	all

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"
-}

Changed12 schema fields changedv3.1.0Aug 22, 2026

addedInput schema / properties / category / title
```
Added value: +"Category"
```

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 20,
+  "description": "Maksymalna liczba wartości metadanych na stronie odpowiedzi (domyślnie 20, maks. 100).",
+  "title": "Limit"
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 0,
+  "description": "Nieujemne przesunięcie strony metadanych.",
+  "title": "Offset"
+}

addedInput schema / title

Added value: +"get_system_metadataArguments"

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"
+  },
+  "MetadataOutput": {
+    "description": "Output for metadata.",
+    "properties": {
+      "category": {
+        "title": "Category",
+        "type": "string"
+      },
+      "count": {
+        "title": "Count",
+        "type": "integer"
+      },
+      "failed_categories": {
+        "default": [],
+        "items": {
+          "type": "string"
+        },
+        "title": "Failed Categories",
+        "type": "array"
+      },
+      "metadata": {
+        "additionalProperties": true,
+        "title": "Metadata",
+        "type": "object"
+      },
+      "page_info": {
+        "$ref": "#/$defs/PageInfo"
+      }
+    },
+    "required": [
+      "category",
+      "metadata",
+      "count",
+      "page_info"
+    ],
+    "title": "MetadataOutput",
+    "type": "object"
+  },
+  "PageInfo": {
+    "description": "Metadata describing one bounded response page.",
+    "properties": {
+      "limit": {
+        "minimum": 0,
+        "title": "Limit",
+        "type": "integer"
+      },
+      "next_offset": {
+        "anyOf": [
+          {
+            "minimum": 0,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Next Offset"
+      },
+      "offset": {
+        "minimum": 0,
+        "title": "Offset",
+        "type": "integer"
+      },
+      "returned_count": {
+        "minimum": 0,
+        "title": "Returned Count",
+        "type": "integer"
+      },
+      "total_count": {
+        "minimum": 0,
+        "title": "Total Count",
+        "type": "integer"
+      },
+      "unit": {
+        "$ref": "#/$defs/PageUnit"
+      },
+      "was_truncated": {
+        "title": "Was Truncated",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "limit",
+      "offset",
+      "returned_count",
+      "total_count",
+      "was_truncated",
+      "unit"
+    ],
+    "title": "PageInfo",
+    "type": "object"
+  },
+  "PageUnit": {
+    "description": "Unit represented by a page.",
+    "enum": [
+      "items",
+      "characters"
+    ],
+    "title": "PageUnit",
+    "type": "string"
+  }
+}

addedOutput schema / properties / data

Added value: +{
+  "$ref": "#/$defs/MetadataOutput",
+  "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[MetadataOutput]"

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 read-only, idempotent, open-world, and non-destructive behavior. The description adds value by specifying what the tool returns and that these values support filtering/searching. It does not contradict the annotations and provides meaningful behavioral context beyond the schema.

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-structured and front-loaded: a one-sentence summary, then a return-value overview, then concrete examples. The example bullets are somewhat repetitive but still earn their place by clarifying expected values for the category parameter.

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?

Given the simple read-only metadata nature, full schema coverage for all three parameters, rich annotations, and presence of an output schema, the description is complete enough for an agent to select and invoke the tool correctly without additional context.

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%, with category, limit, and offset all documented. The description's examples reinforce the category parameter but do not add substantially new semantic meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 states the specific verb 'Pobierz' and the precise resource: metadata of the legal acts system. It clearly enumerates what is returned (keywords, publishers, document types, statuses, institutions), which distinguishes it from sibling tools that deal with documents, search, or filtering results.

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?

It explicitly states the metadata can be used for filtering and searching legal acts, giving the agent a clear context for when to call this tool. It does not name alternative sibling tools or exclusions, but the intended use is clearly implied through the examples and the phrase 'do filtrowania i wyszukiwania aktów prawnych'.

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

Deploy Server