Skip to main content
Glama

Pelnora: Polish law and court rulings

Stan aktu na dzień

get_act
Read-only

Stan aktu: bramka zaufania, stan tekstu na dzień (state), wersja, pochodzenie (TJ / rekonstrukcja, nowele), tytuł, citation. Bez pełnego tekstu; przepisy: get_provision.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eli": "<eli>"
    },
    "name": "get_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
eliYesELI aktu: DU/1974/141 albo DU-1974-141 (Kodeks pracy)
stanNodzień stanu tekstu RRRR-MM-DD (domyślnie dziś)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 real context beyond that — that this is a 'bramka zaufania' (trust gate) exposing provenance and version, and that no full text is returned — but the trust-gate framing is cryptic and return shape/format is not described.

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?

Two short sentences with zero filler, and the resource and returned fields are front-loaded before the get_provision pointer. Density is high, though abbreviations like 'TJ' and 'bramka zaufania' are terse enough to border on opaque.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing return values, and it does list them (state, version, provenance, title, citation) while noting the full-text omission. For a 2-parameter read-only metadata lookup this is nearly sufficient; only the semantics of the 'trust gate' notion and the output shape remain thin.

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%, so both `eli` (with pattern and example DU/1974/141) and `stan` (YYYY-MM-DD, defaults to today) are already fully documented. The description mentions the day-state concept and the ELI-driven identity but adds no syntax, default or format detail beyond the schema. Baseline 3 applies.

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 identifies the resource (akt) and enumerates exactly what metadata the call yields — state as of a date, version, provenance (TJ/rekonstrukcja/nowele), title, citation. It also draws a boundary against the sibling that returns text (get_provision). It is telegraphic field-list phrasing rather than a clean verb+resource sentence, which keeps it from a 5.

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

Usage Guidelines4/5

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

It gives an explicit 'when not' ('Bez pełnego tekstu') and routes the agent to the correct alternative (get_provision) for provisions. What is missing is positive guidance about when to prefer this over get_status, get_timeline or list_acts, but the one disambiguation it does provide is unambiguous.

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