Skip to main content
Glama
Sign In
K-MCP (Korean toolkit for AI agents)

K-MCP (Korean toolkit for AI agents)

by groove79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kr_tax_calendar

Read-onlyIdempotent

Returns Korean tax and payroll filing deadlines for a business profile — VAT, income/corporate tax, withholding, and 4대보험 — with dates shifted to the next business day when they fall on a holiday.

Instructions

Korean tax & payroll filing deadlines for a business profile: VAT (부가세 확정·예정), income/corporate tax, withholding (원천세) and 4대보험 monthly, 지급명세서, 연말정산 — each shifted to the next business day when it falls on a holiday. Filter by month or 'upcoming'. 사업자 유형별 세무·노무 신고 일정을 반환합니다. Use for '이번 달 신고할 것', reminders, cash planning. Needs entity (individual/simplified/corporation/taxfree); employees true if you pay anyone.

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

Input Schema

NameRequiredDescriptionDefault
yearNoDefault: current year (KST)
monthNo
entityNoindividual=개인 일반과세, simplified=간이과세, corporation=법인(12월 결산), taxfree=면세사업자individual
employeesNotrue → 원천세·4대보험·지급명세서 포함
upcomingDaysNoOnly deadlines within N days from today (KST)
extraHolidaysNoAdditional holidays (e.g. from kr_holidays of the public-data server, or company days off)
withholdingHalfYearNo원천세 반기납부 승인 사업자

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / extraHolidays / items / properties / date / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(19|20|21)\\d{2}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / extraHolidays / items / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / extraHolidays / maxItems
      Added value: +500
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add semantics beyond that – and it does, disclosing the non-obvious behavior that deadlines are shifted to the next business day when they fall on a holiday. It does not describe the response shape or how extraHolidays interacts with holiday computation, which would have pushed it higher.

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?

Front-loaded with the resource and scope, then usage, then prerequisites – a sensible ordering. It loses a point for the bilingual redundancy: '사업자 유형별 세무·노무 신고 일정을 반환합니다' restates the opening English sentence without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 optional parameters and no output schema, the description should hint at what a deadline record looks like (date, tax type, filing period, shifted flag) – it does not. It is complete on the input side (entity, employees, date filtering) but leaves the agent guessing about the return structure.

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 86%, so the baseline is 3. The description touches entity and employees meanings, but only restates what the schema already documents (entity enum mapping, employees → 원천세·4대보험·지급명세서); it adds no new semantics for year, month, upcomingDays, extraHolidays or withholdingHalfYear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Korean tax & payroll filing deadlines: VAT 부가세 확정·예정, income/corporate tax, 원천세, 4대보험, 지급명세서, 연말정산) scoped to a business profile, and notes the business-day shifting rule. This is clearly distinguishable from the sibling tools kr_tax_rule, kr_list_holidays and kr_add_business_days, which compute rules or dates rather than return a filing schedule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete use cases ('이번 달 신고할 것', reminders, cash planning) and prerequisites (needs entity; employees true if you pay anyone), plus the filtering modes (month vs upcoming). It lacks an explicit exclusion or routing sentence against the sibling kr_tax_rule, which is the most likely source of confusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools