Skip to main content
Glama

Is it a Korean business day?

kr_business_day
Read-onlyIdempotent

Check whether a date is a business day in South Korea (not a weekend and not a public holiday), and give the previous and next 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kr_business_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-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

A3.7/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 genuinely useful behavior beyond that: the holiday dataset window (2024-2027), its source and refresh date, and that substitute holidays, election days, and specific 2026 additions are included — the coverage limit is the key risk an agent needs to know.

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 what the tool does before the data-provenance details. The 'updated 2026-11-12' stamp and the enumeration of individual 2026 holidays are borderline trivia, but they are compact and arguably relevant to trusting the answer.

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 two-parameter, no-output-schema tool, the description covers purpose, return content (previous/next business days), and the data coverage window — everything needed to call it correctly. It could be a 5 with one line distinguishing the sibling business-day arithmetic tools.

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%, so both parameters (date with KST default, extra_closed_dates) are already documented in structured data. The description adds no format or semantics beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ('Check whether a date is a business day in South Korea') and even defines the criteria (not a weekend, not a public holiday) plus an extra output (previous and next business days). It is clear enough to separate from siblings like kr_holidays, but it does not name any alternative, so an agent must infer when to prefer kr_add_business_days or kr_count_business_days.

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 only implied by the purpose statement; there is no explicit 'use this when…' or 'do not use for…' guidance. The agent can guess this is the single-date check tool versus the arithmetic siblings, but nothing in the text routes it there.

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.