Skip to main content
Glama

Pelnora: Polish law and court rulings

Stan bazy Pelnory

get_status
Read-only

Świeżość bazy (asOf.prawo: dzień bazy prawa, czyli ostatni udany przebieg prawa albo dzień ostatniej pełnej publikacji, jeśli późniejszy; ostatnia pełna publikacja prawa, pole fullPublication: OK / STALE po 48 h / UNKNOWN; najnowsze orzeczenie per typ sądu), liczby aktów per bramka i orzeczeń per typ sądu. unitTextUncertain: liczba przepisów z tekstem niepewnym (stan TEXT_UNCERTAIN), OK / STALE / PARTIAL (liczba niepełna) / UNKNOWN. coverage: per akt z tekstem coveredFrom (od tego dnia jest tekst; wcześniej NOT_COVERED), versions, currentFrom; ze stan także coveredOnDay (czy akt ma tekst na ten dzień) i ich liczba.

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": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
stanNodzień RRRR-MM-DD: które akty mają tekst na ten dzień (coverage.coveredOnDay)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 safety is covered structurally. The description does add genuine behavioral context beyond annotations — the 48 h staleness threshold for fullPublication, the OK/STALE/PARTIAL/UNKNOWN state vocabulary, and the NOT_COVERED-before-coveredFrom semantics. It stops short of describing overall response shape or whether the status is computed live versus cached.

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 text is compact with no filler, but it is a single dense run-on with nested parentheses and no hierarchy, mixing return-field semantics and parameter explanation in one block. It is front-loaded with the topic ('Świeżość bazy') but not with a purpose statement, making it hard to parse.

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 explaining return values, and it does enumerate the significant fields (asOf.prawo, fullPublication, unitTextUncertain, coverage.coveredFrom/versions/currentFrom/coveredOnDay) plus their standing values. What is missing is the top-level shape of the response and any statement of how the per-bramka and per-typ-sądu aggregates are keyed.

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% and the single parameter already documents the YYYY-MM-DD format. The description's tail clause restates the same meaning ('które akty mają tekst na ten dzień (coverage.coveredOnDay)'), adding only the cross-reference to the coverage field — meaningful but marginal. Baseline 3 applies when the schema does the heavy lifting.

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

Purpose3/5

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

The description enumerates what data the tool exposes ('Świeżość bazy', counts of acts per bramka and rulings per court type, unitTextUncertain, coverage), which effectively identifies it as a database-status/freshness tool. However there is no verb and no single statement of what the tool does — the agent must infer the purpose from a field dump. It is distinguishable from siblings like get_act or get_ruling only by the content listed, not by an explicit scope statement.

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

Usage Guidelines2/5

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

No when-to-use guidance is given, no mention of alternatives, and no note on when the optional 'stan' date should be supplied versus omitted. The only hint is the inline gloss that 'stan' selects coverage for a given day, which implies usage but never states it.

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