Skip to main content
Glama
Nolpak14

getregdata

by Nolpak14
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

regdata_slovakia_rpvs_ubo

Search Slovakia's public beneficial-ownership register by company IČO or name. Retrieve UBO details with PEP flags and authorised person for KYC/AML and compliance checks.

Instructions

Slovakia RPVS Beneficial Owners (UBO) Scraper. Search Slovakia's public beneficial-ownership register (RPVS) by IČO or company name. Returns beneficial owners with a public-official (PEP) flag, plus the authorised person. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxItemsNoOptional cap on billed dataset items returned.
exactMatchNoOff (default): contains-search. On: match the company name exactly.
icoNumbersNoOne or more Slovak IČO registration numbers (e.g. "35763469"). Used when search mode is "By IČO".
maxResultsNoMaximum partner records to export across all queries.
searchModeNoLook up by Slovak company registration number (IČO), or search by company name.byIco
currentOnlyNoOff (default): include historical beneficial owners and identities. On: keep only currently-valid entries.
searchQueryNoCompany name to search (contains-match on the partner's registered name). Used when search mode is "By company name".

Schema Changelog

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

  1. Changed7 schema fields changedv1.0.4
    • removedInput schema / description
      Removed value: -"Input for regdata/slovakia-rpvs-ubo-scraper. Freeform - matches the actor's Apify input schema."
    • addedInput schema / properties / currentOnly
      Added value: +{
+  "default": false,
+  "description": "Off (default): include historical beneficial owners and identities. On: keep only currently-valid entries.",
+  "title": "Current entries only",
+  "type": "boolean"
+}
    • addedInput schema / properties / exactMatch
      Added value: +{
+  "default": false,
+  "description": "Off (default): contains-search. On: match the company name exactly.",
+  "title": "Exact name match",
+  "type": "boolean"
+}
    • addedInput schema / properties / icoNumbers
      Added value: +{
+  "description": "One or more Slovak IČO registration numbers (e.g. \"35763469\"). Used when search mode is \"By IČO\".",
+  "title": "IČO numbers",
+  "type": "array"
+}
    • addedInput schema / properties / maxResults
      Added value: +{
+  "default": 50,
+  "description": "Maximum partner records to export across all queries.",
+  "title": "Max results",
+  "type": "integer"
+}
    • addedInput schema / properties / searchMode
      Added value: +{
+  "default": "byIco",
+  "description": "Look up by Slovak company registration number (IČO), or search by company name.",
+  "enum": [
+    "byIco",
+    "byName"
+  ],
+  "title": "Search mode",
+  "type": "string"
+}
    • addedInput schema / properties / searchQuery
      Added value: +{
+  "description": "Company name to search (contains-match on the partner's registered name). Used when search mode is \"By company name\".",
+  "title": "Company name",
+  "type": "string"
+}
  2. First observedv1.0.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It mentions the tool is a scraper and returns certain data, but lacks details on error handling, rate limits, or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the core purpose and key details without unnecessary fluff.

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?

Given that there is no output schema and no annotations, the description is reasonably complete. It explains the tool's function, return data, and mentions additional fields, though it could detail output structure more.

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% with clear parameter descriptions. The tool description adds minimal extra meaning beyond the schema, such as noting advanced fields available via regdata_describe.

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 the tool searches Slovakia's beneficial-ownership register by IČO or company name, returning beneficial owners with PEP flag and authorised person. This distinguishes it from sibling tools focused on other countries.

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 implies use for Slovakia's register but does not explicitly state when to use this tool over alternatives or when not to use it. The 'No API key' note provides minor 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