Skip to main content
Glama

Korea Business Days & Holidays

Add Korean business days

kr_add_business_days
Read-onlyIdempotent

The date that is N business days after (or before, if negative) a date in Korea. The start date itself is not counted. Use for deadlines like 'within 5 business days'.

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

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD (Korea date)
daysYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description adds genuine semantics on top: the counting convention ('the start date itself is not counted') and that a negative input moves backward. It does not spell out whether Korean public holidays are skipped or how the 500-day bound behaves, which keeps it from a 5.

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?

Two tight sentences plus a one-clause usage note. The output shape is front-loaded and the usage example is last, so an agent reads the semantics before the illustration, with no 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?

An output schema exists, so return formatting need not be explained, and annotations carry the safety profile. For a two-param arithmetic tool this covers what is needed, though the treatment of Korean holidays and the ±500 boundary remain undocumented.

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 only 50% – 'days' is documented purely by numeric bounds. The description compensates by explaining the sign convention (negative means before) and the off-by-one counting rule that governs both params, which is real meaning the schema does not supply.

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?

States a specific operation on a specific resource: the date N business days after/before a Korean date. The 'after (or before, if negative)' phrasing and the Korean calendar scope separate it naturally from kr_business_days_between, which counts days rather than shifting them. It never names a sibling explicitly, so it stops short of a 5.

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?

Offers one concrete usage scenario ('within 5 business days' deadlines), which anchors when to reach for it. There is no statement of when not to use it and no pointer to kr_business_days_between or kr_day_info for adjacent needs, so guidance is implied rather than explicit.

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