Skip to main content
Glama
numikel

Law Scrapper MCP

by numikel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Zestawy wyników w pamięci

list_result_sets
Read-onlyIdempotent

Show active result sets with their IDs and pagination metadata to identify which sets are available for filtering legal search results.

Instructions

Wyświetl aktywne zestawy wyników przechowywane w pamięci.

Każde wyszukiwanie (search_legal_acts, browse_acts, track_legal_changes) oraz filtrowanie (filter_results) tworzy zestaw wyników z unikalnym result_set_id. To narzędzie pokazuje aktywne zestawy (TTL: 1h) wraz z metadanymi paginacji.

Kiedy użyć: Aby sprawdzić jakie result_set_id są dostępne do filtrowania. Kiedy NIE używać: Do wyszukiwania nowych aktów → użyj search_legal_acts.

Przykłady:

  • list_result_sets() - Pierwsza strona aktywnych zestawów

  • list_result_sets(limit=5) - Pięć najnowszych wpisów strony

  • list_result_sets(limit=5, offset=5) - Kolejna strona

  • list_result_sets(limit=100) - Wszystkie aktywne zestawy

  • list_result_sets(offset=0) - Jawne przesunięcie od początku

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaksymalna liczba zestawów na stronie odpowiedzi (domyślnie 20, maks. 100).
offsetNoNieujemne przesunięcie strony zestawów. Domyślnie 0.

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. Changed3 schema fields changedv4.2.0
    • addedOutput schema / $defs / ResultSetInfo / properties / scope
      Added value: +{
+  "$ref": "#/$defs/SetScope",
+  "description": "Zasięg zestawu: 'complete' (cały zbiór) albo 'page' (okno z większego zbioru)."
+}
    • changedOutput schema / $defs / ResultSetInfo / required
      Previous value: -[
-  "result_set_id",
-  "query_summary",
-  "result_count",
-  "total_count",
-  "created_at"
-]New value: +[
+  "result_set_id",
+  "query_summary",
+  "result_count",
+  "total_count",
+  "scope",
+  "created_at"
+]
    • addedOutput schema / $defs / SetScope
      Added value: +{
+  "description": "Whether a stored result set is the whole answer or a window into it.",
+  "enum": [
+    "complete",
+    "page"
+  ],
+  "title": "SetScope",
+  "type": "string"
+}
  3. Changed11 schema fields changedv3.1.0
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 20,
+  "description": "Maksymalna liczba zestawó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 zestawów. Domyślnie 0.",
+  "title": "Offset"
+}
    • addedInput schema / title
      Added value: +"list_result_setsArguments"
    • 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"
+  },
+  "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"
+  },
+  "ResultSetInfo": {
+    "description": "Info about a single stored result set.",
+    "properties": {
+      "created_at": {
+        "title": "Created At",
+        "type": "string"
+      },
+      "query_summary": {
+        "title": "Query Summary",
+        "type": "string"
+      },
+      "result_count": {
+        "title": "Result Count",
+        "type": "integer"
+      },
+      "result_set_id": {
+        "title": "Result Set Id",
+        "type": "string"
+      },
+      "total_count": {
+        "title": "Total Count",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "result_set_id",
+      "query_summary",
+      "result_count",
+      "total_count",
+      "created_at"
+    ],
+    "title": "ResultSetInfo",
+    "type": "object"
+  },
+  "ResultSetListOutput": {
+    "description": "Output for listing result sets.",
+    "properties": {
+      "count": {
+        "title": "Count",
+        "type": "integer"
+      },
+      "page_info": {
+        "$ref": "#/$defs/PageInfo"
+      },
+      "sets": {
+        "items": {
+          "$ref": "#/$defs/ResultSetInfo"
+        },
+        "title": "Sets",
+        "type": "array"
+      }
+    },
+    "required": [
+      "sets",
+      "count",
+      "page_info"
+    ],
+    "title": "ResultSetListOutput",
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / data
      Added value: +{
+  "$ref": "#/$defs/ResultSetListOutput",
+  "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[ResultSetListOutput]"
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  4. Addedv1.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by disclosing the TTL (1 hour) for active sets, the in-memory storage, and that it returns pagination metadata. These are behavioral traits not present in annotations, and there is no contradiction.

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 moderately long but well-structured: it leads with the core purpose, then adds context, usage guidance, and examples in a logical flow. Every section serves a purpose, and the examples are compact. It is slightly more verbose than strictly necessary but not wasteful.

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 tool with only 2 optional parameters, an output schema, and comprehensive annotations, the description covers all necessary aspects: purpose, usage, exclusions, examples, and behavioral details like TTL. Nothing an agent needs to call it correctly is missing.

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 both limit and offset fully documented in the input schema. The description's examples illustrate how to use them (e.g., limit=5, offset=5) but add no new semantic meaning beyond what the schema already provides. The baseline of 3 applies here.

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: it lists active result sets stored in memory, each with a unique result_set_id. It differentiates from siblings by explicitly noting it's for checking available result sets for filtering, and it names search_legal_acts as the alternative for new searches. This is a specific verb+resource with clear scope.

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 provides explicit when-to-use (checking which result_set_id are available for filtering) and when-not-to-use (searching for new acts, use search_legal_acts). It also includes multiple usage examples with different parameter combinations, leaving no ambiguity about invocation context.

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