Skip to main content
Glama

Dziennik Firm – Polish company register (KRS) changes

Szukaj spółki

search_companies
Read-onlyIdempotent

Szuka polskiej spółki w bazie Dziennika Firm po nazwie (min. 3 znaki), numerze KRS albo NIP: nazwa, forma prawna, KRS, NIP, REGON, siedziba, status w KRS, url karty. Baza obejmuje spółki z wpisami w KRS od 1 października 2026. Szczegóły i historia wpisów: get_company.

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": {
      "q": "<q>"
    },
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesNazwa spółki, numer KRS albo NIP, np. "JG INVEST", "0000915798".
limitNo

Output Schema

NameRequiredDescriptionDefault
liczbaYes
spolkiYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 safety is covered. The description adds genuinely useful behavior beyond that: the database coverage boundary (companies with KRS entries from 1 October 2026), the exact result fields, and the 3-character query constraint — all of which affect whether a miss means 'not found' vs. 'out of scope'.

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?

Front-loaded with the verb and lookup keys, then the field list, then the coverage caveat and the sibling pointer. The enumerated result fields are somewhat redundant given an output schema exists, but they are compact and readable; no filler sentences.

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?

An output schema exists so return values need not be explained, and the description sensibly spends its space on scope, coverage cutoff, and the get_company escalation path instead. The main gap is that `limit` (default 10, max 50) and paging behavior are left entirely to the schema, and the min-length statement is inconsistent with the schema.

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 50%: `q` is already documented in the schema, and the description adds only the alternate key formats (KRS/NIP) plus the minimum-length rule — which actually conflicts with the schema's minLength=1. The `limit` parameter is never mentioned in the description, so half the parameter surface remains undocumented in both places.

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

Purpose5/5

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

States a specific verb and resource (searching Polish companies in the Dziennik Firm database) and names the accepted lookup keys: name, KRS, NIP. It also enumerates the fields returned, and explicitly routes to get_company for details/history, so the agent can separate it from the sibling without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear use context (lookup by name/KRS/NIP) and names the alternative explicitly: 'Szczegóły i historia wpisów: get_company.' It also states the 3-character minimum for a name query. It stops short of stating when this tool should NOT be used (e.g. full-text article search vs. company lookup), but the contrast with get_company is clear.

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