Skip to main content
Glama

Korea Business Days & Holidays

Count Korean business days

kr_business_days_between
Read-onlyIdempotent

Count business days in Korea between two dates, both inclusive (weekends and public holidays excluded).

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
businessDaysYes

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 readOnlyHint, idempotentHint and openWorldHint=false, so safety and purity need no restating. The description still adds real behavioral content: inclusive endpoints and exclusion of both weekends and Korean public holidays. It does not say what happens if 'to' precedes 'from' or how large a range is allowed, but those are minor gaps for a pure computation tool.

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 sentence with the resource, locale, and counting rule front-loaded; the parenthetical qualification is tight and every phrase carries information.

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?

With an output schema present, return-value behavior need not be described, and both parameters are fully specified in the schema. What remains missing is edge-case behavior (reversed range, very long spans), which keeps it just short of complete for such a simple tool.

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% and both parameters are already documented as YYYY-MM-DD Korea dates, so the baseline would be 3. The description adds genuinely new semantics by stating that both date endpoints are counted, which the schema does not specify and which directly affects how the agent interprets 'from' and 'to'.

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 ('Count business days in Korea between two dates') plus the exact counting rule (both endpoints inclusive, weekends and public holidays excluded). This makes the operation unambiguous and implicitly separates it from kr_add_business_days, but 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'between two dates' — an agent can infer this is the elapsed-count tool rather than the date-shifting or holiday-listing ones, but there is no explicit when-to-use or when-not-to-use guidance.

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