Skip to main content
Glama

Count Korean business days

kr_count_business_days
Read-onlyIdempotent

Count South Korean business days between two dates (both ends included by default). Also returns weekend and weekday-holiday counts. 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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "kr_count_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd YYYY-MM-DD
fromYesStart YYYY-MM-DD
include_endNoCount the end date (default true)
include_startNoCount the start date (default true)
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. Beyond that, the description adds genuinely useful behavior: the inclusive-by-default boundary rule, extra weekend/holiday counts in the response, holiday data range 2024-2027 with source (KASI) and update date, and that substitute holidays, election days and 2026 additions are included. It stops short of saying what happens for dates outside 2024-2027, which is the main behavioral question left open.

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 scope before the data-coverage details. The holiday-coverage sentence is dense with specifics (source, update date, named 2026 additions) that are relevant but could be trimmed without much loss.

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?

There is no output schema, so the description carries the burden of describing returns and does so by naming the weekend and weekday-holiday counts. Data validity bounds are stated, which is critical for a date calculation tool, but out-of-range behavior and the extra_closed_dates override are not covered.

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 the baseline is 3, but the description goes beyond the schema by explaining the net effect of include_start/include_end ('both ends included by default') and by scoping which holiday calendar drives the count. It never mentions extra_closed_dates (company holidays), so one parameter's use case is left entirely to 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 and resource: 'Count South Korean business days between two dates,' with an explicit inclusive-by-default scope and secondary outputs (weekend and weekday-holiday counts). It does not explicitly name or contrast with its closest siblings such as kr_add_business_days or kr_business_day, so differentiation is left to the reader.

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 purpose statement and the inclusive-default caveat, but there is no explicit when-to-use / when-not-to-use guidance and no alternative tool is named. An agent can infer that this is for range counting rather than single-date checks, but must reason it out from sibling names.

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.