Skip to main content
Glama

Pelnora: Polish law and court rulings

Historia aktu: wersje i nowelizacje

get_timeline
Read-only

Oś czasu aktu: daty (ogłoszenie, wejście w życie, uchylenie, wygaśnięcie), teksty jednolite z datą stanu, wersje tekstu [validFrom, validTo) z pochodzeniem (TJ / rekonstrukcja, nowele zastosowane, flagi „z mocą od” / „stosuje się od”), odcinki zamknięte z liczbą jednostek bez tekstu, nowelizacje z datami wejścia w życie transz. Lista tych jednostek tylko z details = units. Tekst wersji: get_act / get_provision z stan = validFrom.

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_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
eliYesELI aktu: DU/1974/141 albo DU-1974-141 (Kodeks pracy)
detailsNounits: lista jednostek bez tekstu raz na odcinek zamknięty; domyślnie same liczby

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 and the bar is lower. The description goes beyond them by disclosing the shape of the returned data, including half-open validity intervals, provenance markers, and the default that closed segments report only counts unless details=units is set. That is exactly the kind of context annotations cannot carry.

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?

It is front-loaded with the most important content (the timeline's components) and contains no filler sentences, but the single run-on paragraph packs many parentheticals and Polish terms into one block, making it hard to scan. Some of it duplicates schema text about details=units.

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?

There is no output schema, so the description must carry the burden of describing the return, and it does so in detail: version intervals, provenance, closed segments, amendment tranches. Combined with a fully documented two-parameter schema, an agent has enough to call it correctly; only the exact response shape (field names, nesting) remains implicit.

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%, and the schema already defines both the ELI pattern with an example and the meaning of details=units, including the default of counts only. The description's mention of details = units largely restates the schema, adding little semantic detail beyond it. Baseline 3 is appropriate.

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 enumerates exactly what the timeline contains for a given act: promulgation/entry-into-force/repeal/expiry dates, consolidated texts with as-of dates, text versions with [validFrom, validTo) ranges and provenance (TJ / reconstruction, applied amendments, 'with effect from' / 'applies from' flags), closed segments with unit-without-text counts, and amendment tranche effective dates. That is far more specific than the bare name and clearly distinct from get_act/get_provision, which it explicitly positions as the place to fetch version text. It loses a point only because the leading phrase names a resource ('Oś czasu aktu') without an explicit verb.

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 concrete routing rules: use details=units to get the list of units rather than just counts, and use get_act / get_provision with stan = validFrom to retrieve the text of a version. That is explicit when-to-use guidance and names the alternatives. It does not state anything about when not to call it or about prerequisites, so it falls short of a 5.

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