Skip to main content
Glama

Pelnora: Polish law and court rulings

Wyszukiwanie aktów z tekstem

list_acts
Read-only

Szuka aktów z tekstem w bazie Pelnory (bramki G1–G3) po fragmencie tytułu albo ELI; wielkość liter bez znaczenia (także polskie litery), bez odmiany wyrazów. Bez query: wszystkie (strony po 50, nextCursor). Ze stan: tylko akty, które mają tekst na ten dzień (wersja z validFrom ≤ stan < validTo), z coveredFrom; akt przed pokryciem nie jest na liście, akt uchylony przed tym dniem jest poza listą albo ma stan REPEALED. Licznik otherDocuments w rulings_for_provision liczy bez filtra stan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_acts"
  }
}

Input Schema

NameRequiredDescriptionDefault
stanNodzień RRRR-MM-DD: tylko akty z tekstem na ten dzień (bez niego: wszystkie akty z tekstem)
queryNofragment tytułu albo ELI
cursorNonextCursor z poprzedniej strony

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavior beyond annotations: page size of 50 with nextCursor, case-insensitive matching including Polish letters, no word inflection, and stan-specific coverage rules involving validFrom/validTo, coveredFrom, and REPEALED. The final sentence about the otherDocuments counter in rulings_for_provision is tangential and does not describe this tool's own behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and remains reasonably compact, but it is a dense run-on paragraph. The final sentence about the otherDocuments counter in rulings_for_provision is unrelated to invoking list_acts and does not earn its place, which lowers conciseness slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining return behavior. It covers pagination (50 per page, nextCursor), coveredFrom, and REPEALED status, but it does not describe the full shape or fields of returned act entries. For a search/list tool with date coverage semantics, this is adequate but leaves gaps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds value beyond the schema: query matches title fragments or ELI, case and Polish letters are ignored, and no word inflection is applied. It also expands stan semantics with validFrom ≤ stan < validTo coverage behavior and notes that acts before coverage are excluded or may appear as REPEALED.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it searches acts with text in the Pelnory database by title fragment or ELI. It is clear and distinct from read-oriented siblings like get_act, but it does not explicitly name an alternative tool to disambiguate when to use this list/search versus fetching a specific act.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful implied usage guidance: without query it returns all acts, and with stan it returns only acts with text on that date. However, it does not explicitly say when to use this tool versus siblings such as get_act or rulings_for_provision, nor does it state exclusions beyond the stan filter behavior.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources