Skip to main content
Glama

4대보험 공제 재료

payroll_pack__insurance_deduction_material_v1__generate

Composite insurance-deduction material v1: combines NHIS, NPS, and COMWEL employment billing notice steps, then returns computed premium totals. The amounts are institution-notice totals billed to the workplace, including BOTH employee and employer portions (employment insurance is the unemployment-benefit portion only); they are NOT the employee payroll-deduction amounts, so compute the employee share separately. Requires prior session login for 건강보험·국민연금·고용산재. To also get income_tax_won and local_income_tax_won from the simplified withholding-tax table, pass employees[] (monthly_pay_won and dependent_count per row) or monthly_pay_won with dependent_count for one employee; without them the tax fields stay in missing_fields. One 고지 (고지년월 + 고지차수) reissued as several NHIS 작성회차 (WRT_CHASU) resolves to the newest revision. When no row key or filter narrows the search to one 고지, each summary uses the newest 고지 of its provider (latest 고지년월, then latest round within it); a tie, or a row whose age cannot be read, stays skipped unless the provider-specific row key disambiguates it. No account_link_id is needed here: each step finds its own institution link. When you combine employee rows from several institutions, treat two rows as the same employee only when BOTH the name and the workplace match; never use a resident registration number (even partial or masked) as the matching key; if two people share a name, do not merge them automatically - ask the user for a distinguishing detail such as the hire date or the institution's employee number; keep an employee found at only one institution and show that institution's amount on its own. If computed is null the result could not be assembled: read computed_error for the reason and do not present the result as complete. Two shapes carry that case: this envelope with partial set to true (we fetched everything - the legs hold it - but could not calculate), or an error whose data carries the same envelope. partial is true whenever the result is incomplete, whether a leg failed or the calculation did. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the pack_run_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": {
      "notice_year_month": "<notice_year_month>",
      "installment_round": "<installment_round>",
      "billing_year": "<billing_year>",
      "billing_month": "<billing_month>"
    },
    "name": "payroll_pack__insurance_deduction_material_v1__generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
employeesNoOptional. One row per employee with monthly_pay_won and dependent_count (children_count_8_to_20 optional, employee_key / employee_name optional labels). When given, the result adds the table income tax and local income tax summed over the rows; without any tax input those fields stay in missing_fields. To tax a single employee, pass monthly_pay_won and dependent_count at the top level instead.
goji_roundNoOptional NHIS notice round
nps_row_keyNoOptional NPS row key from pension notice search. Without it the newest notice is used; pass it to summarize an older notice or to settle a tie between equally new notices
billing_yearYesCOMWEL billing year in YYYY format
nhis_row_keyNoOptional NHIS row key from premium notice search. Without it the newest notice is used; pass it to summarize an older notice or to settle a tie between equally new notices
billing_monthYesCOMWEL billing month 1-12 (string or integer)
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
dependent_countNoADR-069 D-4: >=1 includes self; never invent
idempotency_keyNoOptional outer idempotency key; leg keys are derived deterministically from this value.
monthly_pay_wonNoCanonical monthly pay / gross (ADR-069). Wins over monthly_salary_won when both are set.
nhis_document_idNoNHIS summary document: BMBB_030=regular, BMBB_050=adjustedBMBB_030
installment_roundYesNPS installment round: 1=ED02, 2=ED08
notice_year_monthYesTarget notice year-month in YYYYMM format
business_management_noNoOptional COMWEL business management number; defaults to the logged-in workplace
children_count_8_to_20NoADR-069 D-4: >=0; omit → 0 when monthly pay + dependent_count present

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description goes far beyond them by disclosing token cost per call, XBOSS job creation and result persistence, the 15-minute download_url lifetime and 7-day file retention, the recovery_receipt access model with its explicit non-repairability and do-not-publish warning, and the meaning of partial/computed_error including the two envelope shapes for failure. The Korean sentence confirming the call is not purely read-only is consistent with readOnlyHint=false rather than contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a dense single block that chains unrelated concerns - tax inputs, revision resolution, employee matching rules, failure envelopes, file retention, and recovery receipts - with no headings or sentence breaks. The closing Korean boilerplate about XBOSS jobs and non-read-only behavior partially restates points already made and could be tightened. It is information-rich but over-stuffed for its length.

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 no output schema, 15 parameters, and a multi-institution orchestration, the description does carry most of the burden: it describes artifacts[]/download_url, missing_fields, computed/computed_error, partial semantics, and the employee-merge policy (name AND workplace, never a resident registration number, ask the user on collisions). It does not enumerate what each per-provider summary contains beyond the totals, which leaves a small gap for a tool whose whole output is that summary.

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%, so the baseline is 3, but the description adds genuine meaning the schema does not: it explains the effect of employees[] (adds table income tax and local income tax, otherwise those land in missing_fields), the role of the provider row keys in overriding newest-notice selection or settling ties, and the 고지/작성회차 revision-resolution rule. It stops short of explaining the interplay of notice_year_month, installment_round and billing_year/month against the provider-specific keys.

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?

The first sentence names the verb and resource precisely ('combines NHIS, NPS, and COMWEL employment billing notice steps, then returns computed premium totals'), and the second draws a critical distinction from what an agent would otherwise assume: the amounts are institution-notice totals covering BOTH employee and employer portions, not payroll-deduction amounts. That single clarification separates this tool from the nhis_edi/comwel notice tools and from payslip generation without requiring the agent to open any schema.

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?

Conditional routing is explicit for the main optional path ('To also get income_tax_won ... pass employees[] ... without them the tax fields stay in missing_fields') and for link recovery ('If a link has expired, call xdata__job__result with the pack_run_id'). It also states the login prerequisite for all three institutions and that no account_link_id is needed. What is missing is a direct statement of when to call this composite tool rather than the underlying nhis_edi__hr_payroll__premium_notices__* or comwel__info__individual_billed_premium__* siblings.

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