Skip to main content
Glama

Pelnora: Polish law and court rulings

Przepis (artykuł, paragraf, ustęp…)

get_provision
Read-only

Przepis na dzień ze stanem i zdaniem do cytowania: treść w body (bez oznaczenia), oznaczenie w unitLabel („art. 52 § 1”). Przepis jako „art. 52 § 1” albo ścieżka arti(52)/para(1); indeks górny numeru: „art. 385^1” albo „art. 385(1)”. Stan WORDING_CONFLICT: bez body, wszystkie brzmienia w wordings. Stan TEXT_UNCERTAIN: body podane, ale może być niepełne albo nie tym brzmieniem (kilka brzmień pod ścieżką albo luka w numeracji; powody w stateDetails.textUncertain). Nieistniejący przepis: błąd z listą najbliższych jednostek (nearest); przepis dodany nowelą, której zmiany nie są jeszcze naniesione: ten sam błąd z polem addedNotApplied. Gdy artykułu o podanym numerze nie ma, a jest artykuł, którego numer z indeksem górnym składa się z tych samych cyfr (zamiast „art. 3851” art. 385^1), nearest zaczyna się od niego: to podpowiedź, nie odpowiedź o tym przepisie.

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>",
      "unit": "<unit>"
    },
    "name": "get_provision"
  }
}

Input Schema

NameRequiredDescriptionDefault
eliYesELI aktu: DU/1974/141 albo DU-1974-141 (Kodeks pracy)
stanNodzień stanu tekstu RRRR-MM-DD (domyślnie dziś)
unitYesprzepis: „art. 52 § 1 pkt 3 lit. a” albo ścieżka arti(52)/para(1). Indeks górny numeru: „art. 385^1” albo „art. 385(1)” (także cyfrą w indeksie górnym Unicode), ścieżka arti(385^1); zapis bez znaku indeksu („art. 3851”) oznacza artykuł o takim numerze. Nawias tuż po numerze, bez spacji, to zawsze indeks górny („art. 22(1)” = art. 22^1), nigdy ust. ani §.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnly and closed-world; the description goes far beyond by explaining the WORDING_CONFLICT and TEXT_UNCERTAIN states, which fields are populated in each, and how missing/not-yet-amended provisions surface (nearest, addedNotApplied, stateDetails.textUncertain). That is exactly the behavioral context an agent needs before calling.

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?

Front-loaded with what the tool returns, then state semantics, then error behavior — a sensible order. It is a single dense paragraph and the final sentence about superscript nearest-matching is long, but nearly every clause carries information an agent needs.

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?

There is no output schema, and the description compensates by naming the return fields (body, unitLabel, wordings, stateDetails, nearest) and describing each state's shape. For a three-parameter, state-heavy lookup tool this is complete enough to call correctly on the first try.

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 coverage is 100%, so eli, stan, and unit are already documented with patterns and examples. The description restates unit notation (superscript, path form, 'art. 3851' meaning) and adds only the extra nuance about nearest matching numeric-superscript articles, which is marginal beyond the schema. Baseline 3 fits.

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?

Opens with a specific verb-and-resource statement ('Przepis na dzień ze stanem i zdaniem do cytowania') and names the exact return fields (body, unitLabel). An agent can tell this fetches a single provision as of a date, distinct from get_act or get_timeline.

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?

Usage is implied by the description (fetch one provision for a given stan date), and the accepted unit formats are spelled out at length. However, it never states when to prefer this over get_act, rulings_for_provision, or get_timeline, and offers no explicit exclusion conditions.

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