Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Wydanie dnia: zmiany w KRS

get_daily_edition
Read-onlyIdempotent

Co zmieniło się w polskich spółkach danego dnia (Biuletyn KRS): liczba spółek z wpisami, liczby po rodzajach zmian (nowe spółki, likwidacje, upadłości, restrukturyzacje, wykreślenia, zmiany zarządów…) i pełne listy upadłości, restrukturyzacji i likwidacji. Bez daty: ostatnie zamknięte wydanie.

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

Input Schema

NameRequiredDescriptionDefault
dataNoDzień RRRR-MM-DD (lista dni: list_editions).

Output Schema

NameRequiredDescriptionDefault
urlYes
odczytNo

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, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real value by disclosing the fallback to the last closed edition, but says nothing about response size or limits for the 'full lists', which matters for a read tool that can return large result sets.

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 sentences, front-loaded with the resource and its contents, with the default-date rule placed last where it belongs. The first sentence is dense with parenthetical lists but every item earns its place by defining scope.

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 an output schema present, annotations covering the safety profile, and a single fully described optional parameter, the description supplies what an agent needs to decide and call correctly. The only shortfall is not signalling the potential volume of the returned full lists.

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% and the single date parameter is already documented with its pattern and a pointer to list_editions. The description goes beyond the schema by defining the semantics of omitting the parameter (last closed edition), which is behaviour the schema alone does not convey.

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 names a specific resource (the daily KRS Bulletin edition) and enumerates its contents: counts of companies with entries, breakdowns by change type, and full lists of bankruptcies, restructurings and liquidations. This clearly separates it from company-level siblings like get_company or search_companies, though it never explicitly names an alternative.

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 content description (a daily digest, not a per-company lookup), and the 'Bez daty' clause usefully states the default behaviour when no date is supplied. However, there is no explicit when-to-use/when-not guidance and no routing to a sibling for per-company or per-event questions.

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