Skip to main content
Glama

Check Korean business registration numbers

kr_business_number_check
Read-onlyIdempotent

Validate the format and check digit of South Korean business registration numbers (사업자등록번호, 10 digits, NTS weights 1,3,7,1,3,7,1,3,5) and format them as 123-45-67890. This is an offline checksum test only: it does not tell whether the business is open or closed.

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": {
      "numbers": "<numbers>"
    },
    "name": "kr_business_number_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersYesUp to 1000 numbers, any punctuation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds genuine behavioral context beyond them: the check is offline and deterministic (fixed NTS weights), and a successful check carries no claim about business status — a semantic caveat an agent could not infer from annotations.

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?

Two sentences, front-loaded with the core operation and capped by the most important caveat. The inclusion of the literal weight sequence (1,3,7,1,3,7,1,3,5) is arguably more detail than an agent needs to select the tool, but it does document determinism and costs only a parenthetical.

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

Completeness3/5

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

With no output schema, the description must carry return-value structure, and it only partially does: it states the numbers are formatted as 123-45-67890, but not whether the result is a list of strings, objects with per-number validity flags, or how failures are reported for a batch that mixes valid and invalid entries. For a batch tool accepting up to 1000 items, that partial-result behavior is a meaningful gap.

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 description coverage is 100% and the single parameter already documents 'Up to 1000 numbers, any punctuation', so the schema carries the parameter burden. The description adds nothing new about input handling (e.g., what happens to a malformed entry mid-list) — the '123-45-67890' example describes output formatting rather than input semantics, so baseline 3 applies.

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 pair: validate the format and check digit of South Korean business registration numbers, and formats them. It even names the exact number system (사업자등록번호, 10 digits) and the checksum weighting, so an agent knows precisely what operation is performed and can distinguish it from any of the sibling formatting/conversion 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 clause 'This is an offline checksum test only: it does not tell whether the business is open or closed' is an explicit when-not boundary that prevents a common misuse (treating a pass as proof the company is registered/active). It lacks named alternatives for the case where an agent does need live business-status verification, so it falls short of a full 5.

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.