Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Zdarzenia w KRS z filtrami

list_events
Read-onlyIdempotent

Wpisy w KRS rozpoznane jako zdarzenia (np. nowe spółki, likwidacje, upadłości, zmiany zarządów) z filtrami: typ, dzień albo zakres dat, województwo; od najnowszych, ze stronicowaniem. Każda pozycja: data, rodzaj zmiany, spółka (nazwa, KRS, siedziba), url karty.

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

Input Schema

NameRequiredDescriptionDefault
doNoDo dnia.
odNoOd dnia.
typNoRodzaj zdarzenia (list_event_types).
wojNoWojewództwo siedziby (slug).
dataNoJeden dzień.
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
liczbaYes
zdarzeniaYes

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is lighter. It adds real value beyond them by disclosing sort order (newest first), pagination, and the shape of each returned item (date, change type, company name/KRS/seat, card url).

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?

The definition is a single dense sentence that front-loads the resource and examples, then filters, ordering, pagination, and return fields. It is efficient, though the run-on structure makes the filter list slightly harder to scan than separated clauses would be.

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 and annotations covering safety, the description needs only to explain purpose and filtering, which it does. Minor omissions remain: precedence between the single-day and range date parameters, default/maximum limits, and no pointer to the event-type lookup tool.

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 71%, and the description compensates by grouping the filter parameters and clarifying that the date filter is either a single day or a range. It also glosses 'woj' as the voivodeship of the registered seat. It does not explain how 'data' interacts with 'od'/'do' or mention limit/offset bounds, leaving some ambiguity.

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 (KRS entries classified as events) and enumerates concrete event kinds (new companies, liquidations, bankruptcies, management changes), so an agent knows exactly what the tool returns. It does not explicitly differentiate itself from siblings such as list_event_types, which remains a gap.

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?

It states the available filters and that results come newest-first with pagination, which implies the browsing use case. However, it gives no explicit when-to-use or when-not-to-use guidance and never routes the agent to list_event_types to discover valid type values, even though that tool exists.

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