Skip to main content
Glama

지방소득세 특별징수 신고 제출

wetax__tax__local_income__special_withholding__submit
Destructive

먼저 호출할 도구: wetax__session__login (같은 account_link_id). 기관에 한 번 제출합니다(실제 신고). 세 확인값(confirm_submit, confirm_amounts_reviewed, confirm_legal_effect)이 모두 true 여야 하고, 하나라도 빠지면 아무것도 보내지 않습니다. 제출한 신고는 미납이고 납부기한이 지나지 않았을 때만 신고 취소 도구로 취소할 수 있습니다. 결과를 확인하지 못하면 그렇게 답하고 자동으로 다시 보내지 않습니다 - 다시 보내기 전에 신고 이력 조회로 확인합니다. 납부는 하지 않습니다. 요청 처리 시 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": {
      "dclr_id": "<dclr_id>",
      "confirm_submit": "<confirm_submit>",
      "confirm_amounts_reviewed": "<confirm_amounts_reviewed>",
      "confirm_legal_effect": "<confirm_legal_effect>"
    },
    "name": "wetax__tax__local_income__special_withholding__submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dclr_idYes신고 식별자입니다. 신고인 저장이 돌려준 값을 그대로 넣습니다.
confirm_submitYes제출하겠다는 확인으로 true 를 보냅니다. true 가 아니면 거절합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
confirm_legal_effectYes제출한 신고에 법적 효력이 있다는 점을 확인하는 뜻으로 true 를 보냅니다. true 가 아니면 거절합니다.
confirm_amounts_reviewedYes제출 전에 검토 결과로 금액과 대상자를 확인했다는 뜻으로 true 를 보냅니다. true 가 아니면 거절합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / confirm_amounts_reviewed / description
      Previous value: -"Must be true. Confirms the amounts were reviewed."New value: +"제출 전에 검토 결과로 금액과 대상자를 확인했다는 뜻으로 true 를 보냅니다. true 가 아니면 거절합니다."
    • changedInput schema / properties / confirm_legal_effect / description
      Previous value: -"Must be true. Confirms the filing has legal effect."New value: +"제출한 신고에 법적 효력이 있다는 점을 확인하는 뜻으로 true 를 보냅니다. true 가 아니면 거절합니다."
    • changedInput schema / properties / confirm_submit / description
      Previous value: -"Must be true. Confirms the submission."New value: +"제출하겠다는 확인으로 true 를 보냅니다. true 가 아니면 거절합니다."
    • changedInput schema / properties / dclr_id / description
      Previous value: -"Draft filing ID returned by the declarant step."New value: +"신고 식별자입니다. 신고인 저장이 돌려준 값을 그대로 넣습니다."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds materially: the three-way confirmation gate that prevents partial sends, the cancellation window constraint, the no-auto-resend rule, the fact that no payment occurs, and that an XBOSS task is created with the result stored. The statement '이 호출은 순수 읽기 전용이 아닙니다' reinforces rather than contradicts the annotations.

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?

The prerequisite tool call is front-loaded in the first clause, followed by scope, gating, and recovery in a logical order. A few sentences are near-boilerplate ('요청 처리 시 XBOSS 작업을 생성하고...', '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다') and could be trimmed, but nothing is redundant with the schema.

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?

For a destructive, irreversible-in-effect filing tool with no output schema, the description covers everything an agent needs: prerequisite authentication, confirmation gating, what is and is not performed (no payment), post-submission cancellation limits, and what to do when the outcome is uncertain. The 100% schema coverage handles parameter detail.

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 per-parameter meanings are already documented, but the description adds the collective semantics that all three confirm values must be true simultaneously and that any missing one results in no transmission. It also ties account_link_id to the login call's identifier. The remaining addition is modest, so this sits just above the baseline.

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 verb and resource ('기관에 한 번 제출합니다(실제 신고)') and immediately marks it as the real filing rather than a draft. It also names the sibling cancel tool and the history-lookup tool, so an agent can distinguish this submission step from the surrounding declarant_save/review/cancel steps without opening 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 Guidelines5/5

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

Gives an explicit prerequisite (call wetax__session__login first with the same account_link_id), an explicit gating condition (all three confirm flags must be true or nothing is sent), and explicit alternatives (cancel tool only while unpaid and before the deadline; search_history before any resend). When-to-use, when-not-to-use, and recovery routing are all covered.

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