Skip to main content
Glama
Nolpak14

getregdata

by Nolpak14
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

regdata_msig

Search the Polish Court and Economic Gazette for bankruptcy, liquidation, restructuring, and creditor notices. Full-text archive from 2001, structured JSON output for screening and monitoring.

Instructions

Poland MSiG Court Gazette Scraper. Search Polish Court & Economic Gazette (Monitor Sądowy i Gospodarczy) for bankruptcy declarations, liquidation notices, restructuring proceedings, creditor calls. Full-text search across archive from 2001. Structured JSON output. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
krsNoSearch by KRS number (10 digits)
nipNoSearch by NIP (Tax ID)
dateToYesPublication date range end (YYYY-MM-DD). Required.
dateFromYesPublication date range start (YYYY-MM-DD). Required.
maxItemsNoOptional cap on billed dataset items returned.
entityNameNoSearch by entity/company name (partial match)
maxResultsNoMaximum number of results to return. Default: 100. Set to 0 for unlimited.
searchTypeNoA = Announcements database (bankruptcy, liquidation, restructuring, court notices). B = KRS entries database (company registrations, changes — being phased out since Nov 2025).A
textInBodyNoFull-text search in announcement content (max 1000 chars). Use for finding specific terms like 'upadłość', 'likwidacja', etc.
fetchDetailsNoFetch full announcement details (body text) for each result. Slower but returns complete content. If false, returns only list data (no body text).
textInPositionNoSearch in announcement header/position text (max 1000 chars)
signatureOfCaseNoSearch by court case signature (sygnatura)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed13 schema fields changedv1.0.4
    • removedInput schema / description
      Removed value: -"Input for regdata/msig-scraper. Freeform - matches the actor's Apify input schema."
    • addedInput schema / properties / dateFrom
      Added value: +{
+  "description": "Publication date range start (YYYY-MM-DD). Required.",
+  "title": "Date From",
+  "type": "string"
+}
    • addedInput schema / properties / dateTo
      Added value: +{
+  "description": "Publication date range end (YYYY-MM-DD). Required.",
+  "title": "Date To",
+  "type": "string"
+}
    • addedInput schema / properties / entityName
      Added value: +{
+  "description": "Search by entity/company name (partial match)",
+  "title": "Entity Name",
+  "type": "string"
+}
    • addedInput schema / properties / fetchDetails
      Added value: +{
+  "default": true,
+  "description": "Fetch full announcement details (body text) for each result. Slower but returns complete content. If false, returns only list data (no body text).",
+  "title": "Fetch Full Details",
+  "type": "boolean"
+}
    • addedInput schema / properties / krs
      Added value: +{
+  "description": "Search by KRS number (10 digits)",
+  "title": "KRS Number",
+  "type": "string"
+}
    • addedInput schema / properties / maxResults
      Added value: +{
+  "default": 100,
+  "description": "Maximum number of results to return. Default: 100. Set to 0 for unlimited.",
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / nip
      Added value: +{
+  "description": "Search by NIP (Tax ID)",
+  "title": "NIP Number",
+  "type": "string"
+}
    • addedInput schema / properties / searchType
      Added value: +{
+  "default": "A",
+  "description": "A = Announcements database (bankruptcy, liquidation, restructuring, court notices). B = KRS entries database (company registrations, changes — being phased out since Nov 2025).",
+  "enum": [
+    "A",
+    "B"
+  ],
+  "title": "Search Type",
+  "type": "string"
+}
    • addedInput schema / properties / signatureOfCase
      Added value: +{
+  "description": "Search by court case signature (sygnatura)",
+  "title": "Case Signature",
+  "type": "string"
+}
    • addedInput schema / properties / textInBody
      Added value: +{
+  "description": "Full-text search in announcement content (max 1000 chars). Use for finding specific terms like 'upadłość', 'likwidacja', etc.",
+  "title": "Text in Body",
+  "type": "string"
+}
    • addedInput schema / properties / textInPosition
      Added value: +{
+  "description": "Search in announcement header/position text (max 1000 chars)",
+  "title": "Text in Position",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "dateFrom",
+  "dateTo"
+]
  2. First observedv1.0.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, yet description omits critical behavioral traits such as authentication, rate limits, pagination, or error handling. Only mentions fetchDetails slows down but returns complete content. Significant gaps for a parameter-heavy tool.

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?

Four sentences, front-loaded with purpose. Could be slightly more structured, but no fluff. The reference to regdata_describe is appropriate but adds a minor complexity.

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?

Lacks explanation of output structure (JSON format unspecified) and how date range works. No details on search type differences. With 12 parameters and no output schema, more context would help agent select correctly.

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 100%, so baseline holds. Description adds little beyond schema: mentions full-text search character limits and partial matching, but already present. The note about accepting advanced fields via regdata_describe is helpful but minor.

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?

Clearly states it searches Polish Court & Economic Gazette for bankruptcy, liquidation, restructuring, and creditor calls. Distinguishes from siblings by specifying 'Poland MSiG' and referencing archive from 2001.

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?

Implies usage for Polish economic/legal announcements but lacks explicit when-to-use or comparisons with related tools like regdata_czech_isir_insolvency. No guidance on when not to use.

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