Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Lista wydań

list_editions
Read-onlyIdempotent

Wydania dzienne od najnowszego: data, stan (zamknięte albo w przygotowaniu), liczba spółek z wpisami, nowe spółki, likwidacje, upadłości, restrukturyzacje, wykreślenia, zmiany zarządów.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
urlYes
odczytNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent and closed-world behavior, so the bar is lower; the description adds real value on top by disclosing the sort order and the per-item contents, including the status values 'zamknięte' vs 'w przygotowaniu', which are not encoded anywhere in the schema. It does not discuss pagination or how far back the list reaches, which keeps it from a 5.

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?

A single front-loaded sentence with zero filler; the field enumeration is dense but informative. It reads as a compact list rather than prose, which suits the tool.

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

Completeness3/5

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

Because an output schema exists, the description need not explain return values, and the annotations cover the safety profile for a simple one-parameter read tool. The remaining gaps are the undocumented limit parameter and the absence of any routing against get_daily_edition, leaving it merely adequate overall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, and the description never mentions 'limit' at all. The schema's default of 14 and maximum of 90 are self-evident from the constraints, but there is no explanation of what the limit counts or how it interacts with the newest-first ordering, so the description does not compensate for the coverage gap.

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 clearly identifies the resource (daily editions) and its ordering (newest first), and even enumerates the fields each edition carries. The verb is implied rather than stated, and nothing distinguishes it from the sibling get_daily_edition, so it stops short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives; an agent cannot tell from this text whether to call list_editions or get_daily_edition. Usage is only inferable from the noun 'list' and the newest-first ordering.

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