Skip to main content
Glama

Korea Number & Format Checks

Normalize a Korean phone number

kr_normalize_phone
Read-onlyIdempotent

Normalize a Korean phone number to display form (010-1234-5678, 02-123-4567, 1588-1234) and E.164 (+821012345678), and tell its kind (mobile, Seoul, area code, nationwide 15xx/16xx/18xx, internet 070).

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": {
      "phone": "<phone>"
    },
    "name": "kr_normalize_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes

Output Schema

NameRequiredDescriptionDefault
validYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's job is to add behavior — which it does by naming both output representations and the classification taxonomy (mobile, Seoul, area code, nationwide 15xx/16xx/18xx, internet 070). It stops short of stating what happens on unparseable input, which is the main remaining behavioral question.

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?

A single sentence that front-loads the primary output form and appends the alternate representation and classification without any filler. Every element maps to a distinct piece of information an agent needs.

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?

An output schema exists, so return-value explanation is not required, and the tool is a one-parameter pure function with annotations covering safety and determinism. Given that complexity level, the description supplies everything essential except edge-case error behavior.

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 one parameter with 0% schema description coverage, so the description must carry the parameter meaning; it establishes the input domain as Korean numbers but never says which input shapes are accepted (hyphens, spaces, +82 prefix, numbers without a leading zero). The lenient 4-30 character bound in the schema is not reconciled with any stated acceptance rules.

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 (normalize) and resource (Korean phone number), then enumerates the exact output forms (010-1234-5678, 02-123-4567, 1588-1234, +821012345678) and the classification it produces. The resource is unambiguous against siblings like kr_check_business_number and kr_amount_in_words, which operate on different inputs.

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?

Usage is implied by the domain specificity of the resource rather than stated: nothing says when to call this versus a validation or formatting tool, and no exclusions or prerequisites are given. For a single-purpose normalization utility aimed at Korean numbers, an agent can still infer the use case, but the guidance is implicit.

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