Skip to main content
Glama

regdata_polish_regon

Fetch Polish company data from GUS REGON by NIP, REGON, or KRS. Get PKD codes, local units, and full reports anonymously without an API key.

Instructions

Polish REGON Scraper - GUS Business Registry (no API key). Scrape Poland's REGON (GUS) registry anonymously: look up by NIP/REGON/KRS, discover companies by address + PKD, and get local units (jednostki lokalne) as separate rows. No API key required. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fetchPkdNoAdditionally fetch each entity's PKD activity codes (main + secondary).
maxItemsNoOptional cap on billed dataset items returned.
pkdCodesNoKeep only records whose PKD code starts with one of these (e.g. "10", "62.01"). Requires fetchPkd.
pkdMatchNo'main' = only the main (przeważająca) PKD must match; 'any' = any reported PKD may match.any
legalFormsNoKeep only entities whose legal form contains one of these phrases (e.g. "spółka z ograniczoną", "spółka akcyjna").
maxResultsNoMaximum records to emit (0 = unlimited). Bounds cost on large regions.
searchModeNoHow to look up companies: by NIP, REGON, or KRS number.nip
identifiersNoThe NIP, REGON, or KRS numbers to look up (one search mode at a time).
pkdSectionsNoKeep only records with a PKD code in these PKD 2007 sections. C=Manufacturing, G=Trade, H=Transport, etc. Requires fetchPkd.
minIntervalMsNoPoliteness delay between requests. The site allows ~3/s; keep >= 350ms to avoid the conditional CAPTCHA.
fetchFullReportNoFetch each entity's full REGON report (legal form, ownership, dates, contact, full address). Adds one request per record.
includeLocalUnitsNoInclude each entity's local units (jednostki lokalne) as separate rows (recordType=LOCAL_UNIT, with parentRegon).
Behavior4/5

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

The description discloses important behaviors: no API key required, anonymous scraping, acceptance of additional properties, and delay recommendations (minIntervalMs) to avoid CAPTCHAs. It references regdata_describe for advanced fields. However, it does not detail response format or error handling.

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 description is a single focused paragraph that conveys key information efficiently. It is front-loaded with the tool's name and core feature (no API key). Minor improvement could be structuring with bullet points, but it is not verbose.

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?

The description covers the main use cases, anonymity, and the possibility to fetch local units. It references regdata_describe for additional fields. Given the lack of output schema, it provides adequate context, though it could mention common error states.

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 description coverage is 100%, so baseline is 3. The description does not add further meaning to parameters beyond what is in the schema. It mentions extensibility via additional properties but does not elaborate on any specific parameters.

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?

The description clearly states it is a Polish REGON scraper for the GUS Business Registry, explaining it can look up by NIP/REGON/KRS, discover companies by address and PKD, and fetch local units. This distinguishes it from sibling tools which target other countries or specific registries.

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?

The description does not explicitly state when to use this tool over alternative Poland-specific tools like regdata_poland_kyb_check or regdata_poland_krs_financial. It implies use for REGON scraping but lacks comparative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server