Korea Business Verify (KBV)

Batch check Korean business status

check_korean_business_batch

Read-onlyIdempotent

Screen a list of up to 100 Korean businesses in a single call by their 10-digit business registration numbers (사업자등록번호). Returns one entry per input number (order preserved) with registration status, tax type, and any public-procurement debarment ("부정당업자 제재") on record — a company can be perfectly active and still barred from public contracts. The summary counts how many are currently debarred. Use this for supplier, vendor or customer list screening instead of repeated single checks. Recently checked numbers may be answered from a cache up to 24 hours old (marked "cache": true). Sources: Korea National Tax Service, Public Procurement Service.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`business_numbers`	Yes	1-100 Korean business registration numbers; hyphens/spaces allowed

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes
`summary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / results / items / properties / sanctions

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "active": {
+        "type": "boolean"
+      },
+      "begins_on": {
+        "type": "string"
+      },
+      "ends_on": {
+        "type": "string"
+      },
+      "institution": {
+        "type": "string"
+      },
+      "law": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "active"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / summary / properties / sanctioned
```
Added value: +{
+  "type": "number"
+}
```

First observedSep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the annotations (readOnly/idempotent/openWorld) by disclosing that results may come from a cache up to 24 hours old and are marked with "cache": true, that response order matches input order, and that the summary counts currently debarred companies. It also names the upstream sources (National Tax Service, Public Procurement Service) and the crucial nuance that an active company can still be procurement-debarred.

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?

Front-loads the action, the limit and the identifier before any detail, and each subsequent clause carries information (return shape, debarment caveat, cache, sources). It runs slightly long with parenthetical Korean terms and multiple asides in a single sentence, but nothing is filler.

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?

Covers input constraints, output shape, ordering, caching staleness, summary semantics and data provenance — more than enough for an agent to call this confidently, even though an output schema also exists. The debarment-vs-active distinction in particular prevents a plausible misinterpretation of results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents hyphen/space tolerance, so the baseline would be 3. The description adds real value the schema lacks: the '10-digit' format expectation and the 100-item cap (the schema only sets minItems: 1, with no maxItems). It does not explain ordering of the input array or what happens on partial failures.

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 verb+resource+scale ('Screen a list of up to 100 Korean businesses in a single call') and immediately identifies the input identifier (10-digit 사업자등록번호). The phrase 'instead of repeated single checks' implicitly separates it from the singular sibling check_korean_business_status, so an agent can route without opening any schema.

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?

Gives an explicit use case ('supplier, vendor or customer list screening') and an explicit alternative to avoid ('repeated single checks'). It does not name the sibling tools directly nor mention when a single lookup or find/verify would be preferable, so it stops short of full when/when-not routing.

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

All Korea Business Verify (KBV) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.