Skip to main content
Glama

regdata_belgium_kbo_company

Access official Belgian KBO/BCE company records: identity, status, legal form, address, NACEBEL codes, and named directors. Look up by enterprise/VAT or company name.

Instructions

Belgium KBO/BCE Company Scraper - Directors & VAT. Scrape Belgium's KBO/BCE registry from the official public search: company identity, status, legal form, address, NACEBEL activity codes and NAMED directors/managers. Lookup by enterprise/VAT number or company name. No API key. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
languageNoLanguage of the registry labels/descriptions (NACEBEL activity descriptions, status text). The data itself is identical across languages.en
maxItemsNoOptional cap on billed dataset items returned.
activeOnlyNoWhen searching by name, return only active (non-ceased) entities. Ignored in byNumber mode.
maxResultsNoMaximum number of company records to extract. 0 means no limit. Useful to cap broad name searches.
searchModeNoHow to look up companies. "byNumber" fetches exact companies by enterprise/VAT number (most precise, ideal for KYC/KYB enrichment). "byName" runs the official phonetic name search and then fetches each match.byNumber
searchQueryNoCompany name to search for (used when searchMode = byName). Uses the registry's phonetic search, so minor spelling differences still match. Add a place or legal form to narrow very common names.
minIntervalMsNoPolite delay between requests to the registry. Lower is faster but less courteous; 400ms is a safe default.
enterpriseNumbersNoBelgian enterprise numbers or VAT numbers to look up (used when searchMode = byNumber). Any common format works: "0417.497.106", "0417497106" or "BE0417497106".
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions that it scrapes from the official public search, requires no API key, and includes a polite delay parameter. However, it lacks details on rate limits, caching, or whether it modifies data, leaving some gaps.

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. It front-loads the tool's purpose, lists key data fields, then explains lookup methods and extras. Every sentence contributes information; there is no redundancy.

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 8 parameters with full schema descriptions and no output schema, the description adequately covers purpose, usage, and parameter intent. It could be improved by mentioning the output format or structure, but it lists the types of data returned and references advanced fields.

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?

All 8 parameters have schema descriptions (100% coverage), so the description adds marginal value. It does provide useful context such as phonetic search behavior and the purpose of minIntervalMs, but the schema already covers the basics.

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 scrapes Belgium's KBO/BCE registry and lists specific data fields (identity, status, legal form, address, activity codes, directors). It distinguishes from siblings by specifying Belgium, making it unique among country-specific tools.

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?

The description explains lookup by enterprise/VAT number or company name, and mentions two search modes (byNumber, byName). It references regdata_describe for advanced fields, but does not explicitly state when not to use this tool or provide alternatives.

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