Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Karta spółki z KRS

get_company
Read-onlyIdempotent

Karta spółki po numerze KRS, jak na stronie Dziennika Firm: status, forma, NIP, REGON, siedziba, data wpisu, kapitał, przeważające PKD, organ reprezentujący (bez nazwisk), ostatnie sprawozdanie finansowe, „co wynika z rejestru” (fakty, bez ocen kondycji) i historia wpisów w KRS z rozpoznanymi zmianami (zarząd, siedziba, kapitał, likwidacja, upadłość…).

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": {
      "krs": "<krs>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
krsYesNumer KRS, np. "0000915798".

Output Schema

NameRequiredDescriptionDefault
urlYes
odczytNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: representative organ data is returned without personal names, and register facts are given 'bez ocen kondycji' (no health/quality assessments), which sets accurate expectations about the payload.

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 that opens with the purpose before listing fields. The field enumeration is long but each item informs tool selection; the parenthetical caveats are compact and purposeful rather than filler.

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?

For a one-parameter, read-only lookup with an output schema, the description covers what an agent needs in order to choose and call it correctly. Its only real gap is the absence of guidance on obtaining the KRS number or when to prefer search_companies instead.

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?

There is a single parameter with 100% schema description coverage, including a pattern and a worked example, so the schema carries the semantics. The description only restates that lookup is by KRS number and adds no format, padding, or validation detail beyond the schema.

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 states a specific verb and resource ('Karta spółki po numerze KRS') and enumerates the data returned (status, forma, NIP, REGON, siedziba, kapitał, PKD, organ reprezentujący, sprawozdanie, historia wpisów). The 'by KRS number' framing implicitly separates it from search-oriented siblings like search_companies, but no sibling is named explicitly.

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 only implied: the tool needs a KRS number, which suggests it is a follow-up to a company search, but the description never says so or names an alternative. There is no when-not-to-use guidance or stated prerequisite for obtaining the KRS identifier.

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