Skip to main content
Glama
numikel

Law Scrapper MCP

by numikel
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

read_act_content

Read a specific section or the table of contents of a pre-loaded Polish legal act from Dziennik Ustaw or Monitor Polski. Provide a section identifier (e.g., 'Art. 1') to get its content, or leave empty to list sections.

Instructions

Czytaj treść załadowanego aktu prawnego po sekcjach.

WYMAGANIE: Akt musi być wcześniej załadowany za pomocą get_act_details(eli=..., load_content=True).

Bez parametru section zwraca spis treści (listę sekcji). Z parametrem section zwraca treść wybranej sekcji.

Kiedy użyć: Aby czytać treść konkretnej sekcji załadowanego aktu. Kiedy NIE używać: Aby zobaczyć metadane → użyj get_act_details.

Przykłady:

  • read_act_content(eli="DU/2024/1692") - Spis treści (lista sekcji)

  • read_act_content(eli="DU/2024/1692", section="Art. 1") - Treść artykułu 1

  • read_act_content(eli="DU/2024/1692", section="Rozdział 1") - Treść rozdziału 1

  • read_act_content(eli="DU/2024/1692", section="Dział II") - Treść działu II

  • read_act_content(eli="MP/2024/100") - Spis treści aktu z MP

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eliYesIdentyfikator ELI aktu. Format: "{wydawca}/{rok}/{pozycja}". Wydawcy: DU (Dziennik Ustaw), MP (Monitor Polski). Przykłady: "DU/2024/1716", "MP/2023/500", "DU/2024/1". Akt MUSI być wcześniej załadowany przez get_act_details(eli=..., load_content=True).
sectionNoIdentyfikator sekcji do odczytania. Można użyć surowego ID (np. 'art_1') lub formy czytelnej (np. 'Art. 1', 'Rozdział 1') - obsługiwane jest elastyczne dopasowanie. Aby poznać dostępne section_id, użyj get_act_details(load_content=true) i sprawdź tabelę treści. Jeśli None — zwraca spis treści z dostępnymi sekcjami.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that without section it returns a table of contents, with section it returns content. It mentions flexible matching for section identifiers. Enough for a read-only tool.

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?

Well-structured with clear sections (requirements, usage, examples). Could be slightly shorter but overall effective and easy to parse.

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 two parameters and the presence of an output schema, the description is complete. It covers all use cases, prerequisites, and provides examples. No gaps.

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% but description adds valuable examples for eli format and section flexible matching. It explains that section can be raw ID or readable form, and how to get available sections via get_act_details.

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 reads content of a loaded legal act by sections. It distinguishes from siblings like get_act_details (metadata) and search_in_act (searching). The verb+resource combination is specific and unique.

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?

Explicitly states when to use (reading a specific section) and when not to use (for metadata, use get_act_details). Also specifies the prerequisite that the act must be loaded via get_act_details with load_content=True.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/numikel/law-scrapper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server