Korea Business Verify (KBV)

Check Korean business status

check_korean_business_status

Read-onlyIdempotent

Check the registration status of a Korean business by its 10-digit business registration number (사업자등록번호). Returns whether the business is active, suspended, or closed, plus tax type. Data source: Korea National Tax Service, real-time. The number 1248100998 (Samsung Electronics) is exempt from the daily free tier, so you can exercise this tool while building without spending your allowance.

Input Schema

Name	Required	Description	Default
`business_number`	Yes	10-digit Korean business registration number; hyphens/spaces allowed, e.g. "123-45-67890"

Output Schema

Name	Required	Description	Default
`cache`	Yes
`source`	Yes
`status`	Yes
`tax_type`	Yes
`checked_at`	Yes
`closed_date`	Yes
`business_number`	Yes
`status_code_raw`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- removedOutput schema / properties / closed_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / closed_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so safety is covered. The description adds genuinely useful context beyond them: the data source (Korea National Tax Service, real-time) and a free-tier exemption for the Samsung test number, which is exactly the kind of operational detail annotations cannot express. Return values are partly described but the output schema already covers them.

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?

Three tight sentences, front-loaded with what it does, then what it returns and where the data comes from, then the practical testing note. No sentence is filler and nothing is buried.

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?

For a one-parameter read-only lookup with an output schema and full annotations, the description covers purpose, source, freshness and a useful live-test example. The only gap is sibling differentiation against verify_korean_business, which an agent may hesitate between.

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% and the single parameter already documents the 10-digit format with hyphens/spaces and an example. The description restates the 10-digit requirement and adds the Korean term 사업자등록번호, but contributes no new syntax or constraints beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: check the registration status of a Korean business by its 10-digit registration number, and names the returned status values and tax type. It is clearly a single-record lookup, distinguishing it from the batch sibling, but it does not articulate how it differs from verify_korean_business or find_korean_business.

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 input form (having a 10-digit registration number) is implied clearly enough that an agent knows when this tool applies. However, there is no explicit statement about when to prefer verify_korean_business or find_korean_business, and no exclusions or prerequisites beyond the number format.

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.