Skip to main content
Glama

홈택스 원천세 기한후신고 접수증 조회

hometax__tax__withholding__late_report__receipt

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 제출한 원천세 기한후신고의 접수번호와 접수일을 조회합니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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__late_report__receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_job_idYes이어서 진행할 이전 단계 작업의 job_id 를 그대로 입력합니다(job_ 으로 시작하는 작업 번호). 접수 결과를 찾을 신고서의 작업이면 작성 상태는 묻지 않으므로 제출(submit) 결과나, 제출 결과를 확인하지 못했을 때는 미리보기(preview) 결과를 입력합니다. 같은 조직과 환경, 같은 기관 연결에서 이 신고 유형으로 성공한 작업이어야 하고 아니면 진행하지 않고 거절합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
expected_snapshot_hashYessource_job_id 작업 결과의 snapshot_hash 를 그대로 입력합니다(소문자 16진수 64자리). 그 작업의 내용과 맞지 않으면 진행하지 않고 작성 내용이 바뀌었다는 오류(409)로 거절합니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description explains why: each call consumes one token, creates an XBOSS task, and persists the processing result, so it 'is not pure read-only' even though the institution-side action is a query. That resolves what would otherwise look like a mismatch between a 'lookup' tool and a false readOnlyHint. It also documents the idempotency retry semantics, though it does not describe the return shape or error conditions.

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 statement is buried after a prerequisite line, and the description is a dense run of comma-less Korean sentences blending prerequisite, idempotency protocol, token accounting, and read-only disclosure. The idempotency paragraph is three sentences of protocol boilerplate that would be better placed in a shared note. Little is wasted outright, but the ordering is poor.

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, the description correctly states what comes back (receipt number and receipt date), and with four parameters at full schema coverage the input side needs no more help. The mutation-adjacent behavior (task creation, token cost) and the login prerequisite are covered. Only the error/failure behavior on rejection is missing.

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 coverage is 100% and source_job_id and expected_snapshot_hash are already fully documented in the schema. The description does add usage rules for request_idempotency_key (generate and store before the first request, resend the same value only to recover an unanswered request, and it is unavailable in unauthenticated trial mode), which the schema explicitly defers to the description. However, it contradicts the schema's own wording by describing that field as optional/selectable yet also as a requirement for logged-in calls, and it references an idempotency_key field that is not in this schema at all.

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 second sentence names a specific verb and resource: look up the receipt number and receipt date of a submitted withholding-tax late report. That is far more specific than the title alone. It does not, however, distinguish this tool from the sibling receipt tools (amendment_report__receipt, delete_request__receipt, file_conversion__receipt), so an agent must infer the split from names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description states the prerequisite (call hometax__session__login first with the same account_link_id) and that the target report must already be submitted, which is real routing information. It gives no explicit when-not guidance and no comparison to the other receipt siblings, so the usage context is implied rather than spelled out.

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