Skip to main content
Glama

Korea Number & Format Checks

Validate a Korean business registration number

kr_check_business_number
Read-onlyIdempotent

Check the format and check digit of a Korean business registration number (사업자등록번호, 10 digits) or corporate registration number (법인등록번호, 13 digits). Does not check whether the business is active 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": {
      "number": "<number>"
    },
    "name": "kr_check_business_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNobusiness (default, 10 digits) or corporate (13 digits)
numberYes

Output Schema

NameRequiredDescriptionDefault
validYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and determinism are covered. The description adds the important caveat that a passing check says nothing about business status, which is genuine value beyond the annotations. It does not say what a failure looks like (error vs. negative result), though the output schema likely covers that.

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 tight sentences: the positive scope first, the limitation second. No filler, no restatement of the title, and the key constraint is front-loaded.

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 simple two-parameter validator with an output schema and strong annotations, the description covers purpose, scope and the main caveat. The only residual gap is input formatting tolerance (hyphens/spaces) for the loosely bounded 'number' field.

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 only 50% (the 'number' parameter has no schema description), so the description must compensate, and it does: it specifies 10 digits for business and 13 for corporate, matching the 'kind' enum. It does not clarify whether hyphens or spaces are tolerated in 'number', which the 5-30 length bounds imply are allowed.

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 (check format and check digit) against a precisely named resource, including the Korean term and digit counts for both variants. An agent can tell exactly what is validated and what is not, without opening the 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 clear context for when the tool applies (validating 사업자등록번호 or 법인등록번호) and an explicit exclusion: it does not check whether the business is active or closed. No alternative tools are named, but the siblings listed (amount-in-words, phone normalization) are unrelated, so no routing guidance is needed.

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