Law Scrapper MCP

Overview Schema Source Related Servers Discussions Admin

Dokumenty załadowane do pamięci

list_loaded_documents

Read-onlyIdempotent

Check which legal acts are currently loaded in memory and available for reading or searching. View paginated lists of documents with metadata, and know when documents expire after two hours.

Instructions

Wyświetl dokumenty załadowane do pamięci (Document Store).

Dokumenty ładowane są przez get_act_details(eli=..., load_content=True). Każdy dokument ma TTL 2h — po tym czasie wymaga ponownego załadowania.

Zwraca jedną stronę listy wraz z metadanymi paginacji (page_info).

Kiedy użyć: Aby sprawdzić jakie akty są załadowane i dostępne do czytania/wyszukiwania. Kiedy NIE używać: Do wyszukiwania aktów → użyj search_legal_acts.

Przykłady:

list_loaded_documents() - Wyświetl pierwszą stronę załadowanych dokumentów
list_loaded_documents(limit=5) - Pierwsze pięć dokumentów
list_loaded_documents(limit=5, offset=5) - Kolejna strona
list_loaded_documents(limit=100) - Cała zawartość Document Store
list_loaded_documents(offset=0) - Jawne przesunięcie od początku

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maksymalna liczba dokumentów na stronie odpowiedzi (domyślnie 20, maks. 100).
`offset`	No	Nieujemne przesunięcie strony dokumentów. Domyślnie 0.

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 / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 20,
+  "description": "Maksymalna liczba dokumentów 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 dokumentów. Domyślnie 0.",
+  "title": "Offset"
+}

addedInput schema / title

Added value: +"list_loaded_documentsArguments"

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"
+  },
+  "LoadedDocumentInfo": {
+    "description": "Info about a single loaded document.",
+    "properties": {
+      "eli": {
+        "title": "Eli",
+        "type": "string"
+      },
+      "last_accessed": {
+        "title": "Last Accessed",
+        "type": "string"
+      },
+      "loaded_at": {
+        "title": "Loaded At",
+        "type": "string"
+      },
+      "section_count": {
+        "title": "Section Count",
+        "type": "integer"
+      },
+      "size_bytes": {
+        "title": "Size Bytes",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "eli",
+      "size_bytes",
+      "section_count",
+      "loaded_at",
+      "last_accessed"
+    ],
+    "title": "LoadedDocumentInfo",
+    "type": "object"
+  },
+  "LoadedDocumentListOutput": {
+    "description": "Output for listing loaded documents.",
+    "properties": {
+      "count": {
+        "title": "Count",
+        "type": "integer"
+      },
+      "documents": {
+        "items": {
+          "$ref": "#/$defs/LoadedDocumentInfo"
+        },
+        "title": "Documents",
+        "type": "array"
+      },
+      "page_info": {
+        "$ref": "#/$defs/PageInfo"
+      }
+    },
+    "required": [
+      "documents",
+      "count",
+      "page_info"
+    ],
+    "title": "LoadedDocumentListOutput",
+    "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/LoadedDocumentListOutput",
+  "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[LoadedDocumentListOutput]"

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

Addedv1.0.2Apr 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations, the description discloses critical behavioral details: documents are loaded via get_act_details(eli=..., load_content=True), they have a 2-hour TTL requiring reload, and the tool returns a single page along with page_info. This provides context that the annotations (readOnly, idempotent) do not cover, making the tool's statefulness and lifecycle clear.

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 organized into purpose, lifecycle, return, usage, and examples—front-loaded with a clear one-sentence core. It is a bit longer than strictly necessary, but every sentence adds value, and the structured headers make it easy to scan. It could be tightened slightly, hence a high 4 rather than a 5.

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 an unpaged listing tool with no required parameters, the description is comprehensive: it explains what documents are included, how they get there, TTL, pagination, and returns page_info. Combined with the output schema, an agent has everything needed to invoke and interpret results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for limit and offset, but the description elaborates on practical semantics through examples—showing how limit=100 retrieves the entire store, and mixing limit/offset for page navigation. This transforms the parameters from mechanical API attributes into a mental model for controlling pagination.

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 clearly states the tool's function as listing documents loaded into memory (Document Store), and it explicitly contrasts itself with search_legal_acts in the 'Kiedy NIE używać' section, so an agent can distinguish it from siblings without ambiguity.

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?

The description includes a dedicated 'Kiedy użyć' and 'Kiedy NIE używać' section, explicitly telling the agent to use this tool to inspect loaded acts and pointing to search_legal_acts for searching. It also provides multiple concrete examples covering basic usage, explicit offsets, and page limits, leaving no room for misinterpretation.

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

Deploy Server