v4.1.0

Changelog - v4.1.0

All notable changes to the law-scrapper-mcp project for version v4.1.0 will be documented in this file.

The format is based on Keep a Changelog 1.1.0,
and this project adheres to Semantic Versioning 2.0.0.

[4.1.0] - 2026-09-02

Result-set scope as first-class contract — a single new field disambiguates complete result sets from windows into larger match sets, closing two categories of false inference over stored results.

Added

• Result-set scope: A new set_scope field on every tool response indicates whether the result set is complete (the full set of matches for the query) or page (a window into a larger match set). This directly addresses misinterpretations where a tool returned twenty results from a corpus of thousands but the response implied it was the full set. The scope is stored alongside results in ResultStore and propagates to filter_results, so filtering and paginating both carry the scope forward. Clients that do not use ResultStore can read the scope from result_set_info.set_scope.
• Correct total_count in search_legal_acts: Previously, search_legal_acts reported the current page size as total_count (e.g., 20 when querying a corpus of 1984 matches). The API response carries both count (page size) and totalCount (corpus size) — now the tool reads totalCount, so pagination hints and scope are computed against the actual match count. This reverses a long-standing misreport in the pagination field: was_truncated now correctly reflects whether there are more matches beyond the current page.

Changed

• Pagination hints are now scope-aware: A hint to paginate is only generated when set_scope="page". When set_scope="complete", results cannot be paginated further (the full set fits), so hints encourage filtering instead. This eliminates the prior pattern of suggesting pagination to a tool that was always returning the complete set.