Skip to main content
Glama

홈택스 원천세 수정신고 저장 내용 검토

hometax__tax__withholding__amendment_report__review
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": {
      "source_job_id": "<source_job_id>",
      "expected_snapshot_hash": "<expected_snapshot_hash>"
    },
    "name": "hometax__tax__withholding__amendment_report__review"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_job_idYes이어서 진행할 이전 단계 작업의 job_id 를 그대로 입력합니다(job_ 으로 시작하는 작업 번호). 기본정보 저장(basic_save), 명세 저장(detail_save), 부표 저장(annex_save) 결과처럼 기본정보가 저장된 상태의 결과를 받고, 다시 검토할 때는 검토(review) 결과도 받습니다. 같은 조직과 환경, 같은 기관 연결에서 이 신고 유형으로 성공한 작업이어야 하고 아니면 진행하지 않고 거절하며, 받지 않는 작성 상태의 결과이면 409 로 거절합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
refund_bank_codeNo환급받을 은행의 코드입니다. 숫자 세 자리로 입력합니다. 기본정보의 환급신청 여부가 Y 인 신고서를 검토할 때만 쓰며, 그때 은행 코드와 계좌번호가 모두 있어야 하고 없으면 거절합니다.
refund_account_noNo환급받을 계좌번호입니다. 하이픈 없이 숫자만 1자리에서 20자리까지 입력합니다. 기본정보의 환급신청 여부가 Y 인 신고서를 검토할 때만 쓰며, 그때 은행 코드와 계좌번호가 모두 있어야 하고 없으면 거절합니다.
expected_snapshot_hashYessource_job_id 작업 결과의 snapshot_hash 를 그대로 입력합니다(소문자 16진수 64자리). 그 작업의 내용과 맞지 않으면 진행하지 않고 작성 내용이 바뀌었다는 오류(409)로 거절합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations supply readOnlyHint=false and destructiveHint=true, and the description goes beyond them by disclosing a per-call cost ("호출마다 토큰 1소진"), that an XBOSS job is created and its result persisted, and that the call is not purely read-only even when it reads the institutional original. That directly explains why the annotations mark it non-read-only. It is weaker on mutation impact: the closing line about institutional data changes deferring to per-tool execution and existing confirmation procedures is vague about what is actually altered or reversible.

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 is front-loaded in the first clause, followed by what the tool does and its side-effect profile, which is a sensible order. The final sentence about institutional data changes is boilerplate-ish and could be folded into the side-effect statement without loss.

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?

For a mutation-flagged workflow step with full schema coverage and no output schema, the description covers the prerequisite, ordering before submit, cost, and side effects. What is missing is what the review actually returns or which validation classes it checks, which an agent would want before interpreting the result.

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%, so every parameter, including source_job_id, expected_snapshot_hash, and the refund bank/account pair, is already documented with patterns and rejection conditions in the schema itself. The description adds no parameter-level meaning on top of that, 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 uses a specific verb and resource: it reviews a saved withholding amendment report against the institution's validation criteria ("저장한 원천세 수정신고서를 기관 검증 기준으로 검토합니다"). It is clearly distinct from the save, submit, and history tools, but it never contrasts itself with the closely named preview or requirements siblings, leaving that boundary to inference.

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 gives a concrete precondition ("먼저 호출할 도구: hometax__session__login" with the same account_link_id) and an ordering rule ("제출 전에 부르세요") that tells the agent to call this before submit. It does not say when to use this rather than preview or requirements, and it states no exclusions.

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