Skip to main content
Glama

Basic Dutch company data from the Netherlands Chamber

b2b_netherlands_kvk
Read-only

Basic Dutch company data from the Netherlands Chamber of Commerce (KVK) open High Value Dataset for an 8-digit KVK number: whether the registration is active, start date, legal form code and meaning (BV, NV, sole proprietorship, foundation...), 2-digit postcode region, and SBI activity codes (main and other activities). KVK's open set is anonymised: names and addresses are not included. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "kvk": "<kvk>"
    },
    "name": "b2b_netherlands_kvk"
  }
}

Input Schema

NameRequiredDescriptionDefault
kvkYes8-digit KVK number, e.g. 33302047 (required)

Output Schema

NameRequiredDescriptionDefault
kvkNo
noteNo
activeNo
sourceNo
checkedAtNo
legalFormNo
startDateNo
activitiesNo
memberStateNo
legalFormCodeNo
postcodeRegionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld, so the description carries real weight here and delivers: the dataset is anonymised (no names or addresses), and the pricing model is spelled out ($0.002 per successful call, x402/USDC payment, failed calls free). What it omits is failure behavior for invalid or unknown KVK numbers, which matters for a paid per-call tool.

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?

Two sentences, both front-loaded: identity and payload first, then the critical caveat and cost. Every clause — legal form examples, anonymisation limit, pricing — earns its place for a data-purchase tool, and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param, read-only lookup with an output schema, everything an agent needs is present: what identifies a record, what the record contains, that the record is anonymised, and what a call costs. Return-value structure is already covered by the output schema, so no further explanation is required.

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?

There is a single parameter with 100% schema description coverage including an example value, so the schema already does the work. The description restates the '8-digit KVK number' format but adds no interpretation beyond what is structurally documented, which is the baseline-3 case.

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 resource (Dutch company registration data from KVK's open High Value Dataset) keyed by an 8-digit KVK number, and enumerates exactly what comes back: active status, start date, legal form code and meaning, postcode region, SBI activity codes. That level of specificity distinguishes it immediately from the other b2b_* national-registry siblings.

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 'for an 8-digit KVK number' framing implies the lookup precondition, and the anonymisation note signals what this source can't answer. However, there is no explicit when-to-use or when-not guidance and no named alternative for the case where names/addresses are actually needed — the agent must infer that limitation itself.

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