Skip to main content
Glama

payroll.kr_salary

Read-onlyIdempotent

Calculates Korean net monthly pay from a gross monthly salary, applying 4 major insurances, income tax, local tax, meal allowance limits, dependents, and date-specific policy rules.

Instructions

세전 월급(원, 문자열)에서 한국 실수령액을 구한다. 비과세 식대 한도를 뺀 과세급여로 4대보험 근로자 부담분(국민연금 상·하한, 건강보험, 장기요양, 고용보험)과 근로소득 간이세액표 소득세, 지방소득세(소득세의 10%)를 공제하며 건강보험과 장기요양은 10원 미만 버림, 그 밖의 보험료는 원 미만 버림이고 지방소득세는 징수 끝수 규칙(국고금 관리법 제47조제1항 준용)으로 10원 미만 버림이다. 시행일별 정책을 as_of 로 고른다. 연봉을 월급 자리에 넣으면 안 된다.

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": {
      "monthly_salary": "<monthly_salary>",
      "year": "<year>"
    },
    "name": "payroll.kr_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
as_ofNo
children_8_20No
meal_allowanceNo0
monthly_salaryYes
num_dependentsNo
include_proposedNo

Output Schema

NameRequiredDescriptionDefault
netYes
_metaNo서버가 붙이는 영수증(integrity), 엔진, 힌트
grossYes
taxesYes
traceYes계산 근거(tool, formula, inputs, steps, output)
taxableYes
insurancesYes
non_taxableYes
policy_sha256Yes
policy_sourceYes
policy_statusYes
policy_versionYes적용된 정책 문서의 식별 정보
policy_audit_idYes
policy_citationsYes정책의 근거 조문
income_tax_lookupYes
policy_effective_toYes
policy_effective_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior5/5

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

The annotations already declare readOnly, idempotent, and closed-world, but the description adds substantial behavioral detail beyond them: the exact deduction components (national pension with upper/lower bounds, health, long-term care, employment insurance, simplified tax table income tax, 10% local income tax) and the per-item rounding rules (truncation below 10 won for health/long-term care, below 1 won for other premiums, and the National Treasury Act rounding for local income tax). This is unusually transparent about how the result is produced.

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 correctly front-loaded in the first sentence, but the middle sentence is a dense run-on enumerating insurance components and three different rounding rules, which reads more like implementation notes than agent-facing guidance. The final warning is well placed, but the rounding detail could be compressed without losing selection or invocation value.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. The description thoroughly covers the computation and the as_of policy dimension, but for a seven-parameter payroll tool it leaves the dependent/child/include_proposed parameters and the year-vs-as_of relationship unexplained, which is a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it only partially does: it explains monthly_salary (won, string, monthly not annual), as_of (effective-date policy selection), and alludes to meal_allowance via the non-taxable meal allowance limit. It says nothing about year, children_8_20, num_dependents (default 1), or include_proposed, leaving four of seven parameters — including a required one — undefined in both the schema and the description.

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 opens with a specific verb and resource: it converts a pre-tax monthly salary (in won, as a string) into a Korean net take-home amount, and the gross-to-net direction implicitly distinguishes it from payroll.kr_gross_from_net. It is unambiguous about what is computed, though it never names a sibling tool to make the routing explicit.

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?

The description gives clear context for when to use it: it takes a monthly salary and selects policy by effective date via as_of. It also includes a concrete misuse warning ('연봉을 월급 자리에 넣으면 안 된다'), which prevents the most likely input error. However, it names no alternative tool for adjacent tasks such as reverse net-to-gross or hourly conversions.

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