List available Polish/EU legal data sources, or inspect one source's live tool schemas.

Without arguments: full catalog (id, coverage, capabilities, native tool names, and native_params - the NATIVE parameter name each unified parameter maps to, e.g. eu-compliance pl_get_document -> {"tool": "eu_article", "document_id": "article_number"}) - reads a local registry, spawns nothing. With source_id: connects to that connector (lazy spawn on first use) and returns its live tools/list with input schemas - needed for native tools that the unified tools do not cover. Optional group filter: 'pl' or 'eu'.

Errors: unknown_source (bad source_id), source_unavailable (connector could not start).

Unified search across any registered source (SAOS, NSA, ISAP, EUREKA, KIO, UODO...).

Common parameters are translated to the source's native names (dateFrom vs date_from, 0- vs 1-based pages - handled here; page is ALWAYS 1-based, and is the same parameter name in pl_get_document). date_from/date_to: YYYY-MM-DD. limit: results per page (clamped to the source maximum). extra: source-specific native filters merged verbatim (e.g. {"courtType": "SUPREME"} for saos, {"country": "es"} for legalize - the native names are listed under native_params in pl_list_sources). page_number is a deprecated alias of page; prefer page.

Errors: unknown_source, invalid_arg (source has no search tool, e.g. krs; missing required extra; page < 1), source_unavailable, upstream_error (connector's own error code preserved in message).

Fetch the full document (judgment, act text, register extract...) from a source.

document_id format depends on the source - numeric id (saos), hex doc_id (nsa), ELI (isap), KRS number (krs), signature (kio, uodo)... - see the document_id field in pl_list_sources. Long documents are paginated at ~5000 characters per page: response is JSON with content, page, total_pages, has_more - iterate page while has_more (page is 1-based, exactly as in pl_search; page_number is a deprecated alias kept for backward compatibility, and is echoed in the response for the same reason). Sources that paginate the document themselves (isap) report pagination: "native" and carry their own page footer inside content. Some sources need extra (e.g. eu-compliance: {"regulation": "GDPR"}).

Errors: unknown_source, invalid_arg (missing required extra, page < 1, conflicting page/page_number), source_unavailable, upstream_error (e.g. connector's not_found - check the identifier or search first).

Escape hatch: call any native tool of any registered source.

For operations the unified tools do not cover: citator (saos_cite_check), DPA statistics (uodo_stats), procurement-article search (kio_by_pzp_article), board composition (get_board), regulation comparison (eu_compare), tax category dictionary (list_categories)... arguments (alias: args - both accepted, pass only one) is an object keyed by the NATIVE parameter names of that tool, passed verbatim. The native names of the common ones are in native_params from pl_list_sources; for everything else read the live schema via pl_list_sources(source_id=...). Wrong parameter names are caught here against the connector's schema, before the call leaves the aggregator.

Errors: unknown_source, unknown_tool (not exposed by that source), invalid_arg (missing required or misspelled parameter name), source_unavailable, upstream_error (connector's own error code in message).