Skip to main content
Glama

Korea Business Days & Holidays

Korean public holidays in a range

kr_holidays
Read-onlyIdempotent

List Korean public holidays (관공서 공휴일) between two dates, including substitute holidays (대체공휴일).

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_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesYYYY-MM-DD (Korea date)
fromYesYYYY-MM-DD (Korea date)

Output Schema

NameRequiredDescriptionDefault
holidaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety and repeatability need no restating. The description does add genuinely useful semantic content beyond them by noting that substitute holidays (대체공휴일) are included. It says nothing about whether the interval endpoints are inclusive, the maximum range width, or any result-count limits.

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 tight sentence with no filler; the resource and the substitution-holiday nuance are both front-loaded. Every clause earns its place.

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 read with full schema coverage, an output schema, and complete annotations, the definition is nearly sufficient. The remaining gaps are boundary inclusivity and range-size limits, which are minor but would matter for an agent constructing the query.

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 already carry format and Korea-date semantics. The description only says "between two dates" and does not resolve whether from/to are inclusive, which is the one ambiguity the schema leaves open. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ("List Korean public holidays"), localizes the concept (관공서 공휴일), and scopes it to a date range. This is clearly separable from business-day siblings like kr_business_days_between, though no sibling is named to make the contrast explicit.

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 scope: an agent can infer it queries holidays rather than business days. There is no explicit statement of when to prefer this over kr_day_info or the business-day tools, and no notes on excluded cases.

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