Skip to main content
Glama

Add Korean business days

kr_add_business_days
Read-onlyIdempotent

Move forward (or back, with negative days) a number of South Korean business days from a start date, skipping weekends and public holidays. The start date itself is not counted. Use for deadlines like "within 7 business days". Holiday data covers 2024-2027 (source: KASI; updated 2026-11-12). It includes substitute holidays and election days, and the 2026 additions Labor Day (May 1) and Constitution Day (Jul 17).

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": {
      "days": "<days>"
    },
    "name": "kr_add_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesBusiness days to add; negative goes back.
startNoYYYY-MM-DD. Omit for today in Korea (KST).
extra_closed_datesNoOptional extra non-working dates (YYYY-MM-DD), e.g. company holidays.

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real substance beyond that: negative days move backwards, the start date is excluded from the count, and holiday data only covers 2024-2027 with substitute holidays and election days included. It does not say what happens for dates outside 2024-2027, which is the main remaining behavioral gap.

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?

Three sentences, front-loaded with the core operation and counting rule, then usage, then data coverage. The final clause enumerating specific 2026 holidays (Labor Day, Constitution Day) is somewhat granular but supports trust in the holiday set rather than being pure filler.

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 pure read-only date-arithmetic function with only three fully documented parameters and no output schema, the description covers what matters: counting rule, direction, usage, and data validity window. The return format and out-of-range behavior are left implicit, but an agent has enough to call it correctly.

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%, so baseline is 3; however, the description adds semantics the schema does not spell out, notably that the start date is not counted in the offset, which is essential for boundary correctness. The rest of the parameter meaning (negative days, default start) is already in the schema.

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?

The description states a specific verb (move forward/back a number of business days), a specific resource domain (South Korean calendar), and the exclusions applied (weekends and public holidays, start date not counted). This makes the operation distinguishable in intent from a counting tool, though no sibling is named explicitly.

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?

It gives a concrete usage context: "Use for deadlines like 'within 7 business days'." That is clear when-to-use guidance, but there are no exclusions or pointers to alternatives such as a tool that counts business days between two dates or lists holidays.

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.