Skip to main content
Glama

홈택스 원천세 기한후신고 초안 초기화

hometax__tax__withholding__late_report__init
Destructive

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 귀속연월과 지급연월을 정해 원천세 기한후신고 작성을 시작합니다. 기관에 작성 중인 신고서를 만듭니다. 호출마다 토큰 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": {
      "business_no": "<business_no>",
      "periods": "<periods>"
    },
    "name": "hometax__tax__withholding__late_report__init"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsYes신고 기간 세 값을 담은 객체입니다. submitYm(제출연월), attrYm(귀속연월), pymnYm(지급연월)을 각각 YYYYMM 여섯 자리로 입력하고, 귀속연월이 지급연월보다 늦거나 지급연월이 제출연월보다 늦으면 입력 오류로 거절합니다. JSON 문자열이 아니라 객체로 입력하며 문자열이면 입력 오류로 거절합니다.
draft_modeNo작성 방식입니다. new(기본값)는 새 신고서를 작성하고 resume 은 기관에 저장해 둔 작성 중 신고서를 이어서 씁니다. new 인데 기관에 작성 중인 신고가 이미 있으면 그것을 지우지 않고 409 로 거절하므로, 이어 쓰려면 resume 으로 다시 부릅니다. 다른 값은 입력 오류로 거절합니다.new
business_noYes신고할 사업자등록번호 10자리
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / $defs / Periods / properties / attrYm / description
      Added value: +"귀속연월입니다. 소득이 귀속되는 연월을 YYYYMM 여섯 자리로 입력합니다. 작성 준비(init)에서는 지급연월보다 늦으면 입력 오류로 거절합니다."
    • addedInput schema / $defs / Periods / properties / pymnYm / description
      Added value: +"지급연월입니다. 소득을 지급한 연월을 YYYYMM 여섯 자리로 입력합니다. 작성 준비(init)에서는 제출연월보다 늦으면 입력 오류로 거절합니다."
    • addedInput schema / $defs / Periods / properties / submitYm / description
      Added value: +"제출연월입니다. 신고서를 제출하는 연월을 YYYYMM 여섯 자리로 입력합니다."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses that each call consumes one token, spawns an XBOSS job on the server, persists the result, and creates a draft at the institution. It explicitly warns that the call is not purely read-only, consistent with readOnlyHint=false and destructiveHint=true. The closing sentence about 'per-tool execution and existing confirmation procedures' is boilerplate and adds little.

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?

Sentences are short and front-loaded with the prerequisite, then purpose, then side effects — a sensible order for an agent. The final two clauses about 'institution data changes' are filler that could be cut without loss.

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

Completeness5/5

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

Annotations already declare the destructive/non-read-only profile, the schema fully documents all four parameters including the 409-on-existing-draft case, and the description supplies the missing pieces: prerequisite tool, token cost, job creation, and draft-creating semantics. For a creation tool with no output schema, that is enough to call it correctly.

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 100%, and the schema itself documents the period ordering rules, the new/resume enum, the 409 conflict behavior, and account_link_id fallback in detail. The description only echoes that the attribution and payment year-months are set, adding no meaning beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource — it starts creation of a withholding tax late report ('원천세 기한후신고 작성을 시작합니다') and creates a draft at the institution ('기관에 작성 중인 신고서를 만듭니다'). The explicit '기한후신고' (late report) framing distinguishes it from the regular/amendment init siblings, though no sibling is named directly.

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?

It front-loads a hard prerequisite: call hometax__session__login first with the same account_link_id, which is exactly the ordering an agent needs. It gives clear context (begin a late-report filing) but never states when NOT to use it, and the resume-vs-new decision lives only in the schema, not the description.

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