Skip to main content
Glama

홈택스 원천세 전자파일 변환신고 제출 전 미리보기

hometax__tax__withholding__file_conversion__preview

REQUIRES prior hometax__session__login call with same account_link_id. 내용검증까지 끝나 변환이 완료된 작업에서 제출할 원천세 신고 대상 전체를 보여 줍니다. 변환이 끝나지 않았거나 정상 변환된 대상이 없으면 거절됩니다. 제출하지 않습니다. submit 은 이 단계의 job_id 를 source_job_id 로 받아 미리 본 대상이 그대로일 때만 제출합니다. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 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__file_conversion__preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_job_idYes이어서 진행할 이전 단계 작업의 job_id 를 그대로 입력합니다(job_ 으로 시작하는 작업 번호). 변환이 끝나 제출할 수 있는 상태의 결과를 받습니다. 기관에서 제출 가능한 변환 결과가 없으면 409 로 거절합니다. 같은 조직과 환경, 같은 기관 연결에서 성공한 원천세 파일변환 작업이어야 하고 아니면 진행하지 않고 거절합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
expected_snapshot_hashYessource_job_id 작업 결과의 snapshot_hash 를 그대로 입력합니다(소문자 16진수 64자리). 그 작업의 내용과 맞지 않으면 진행하지 않고 작성 내용이 바뀌었다는 오류(409)로 거절합니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that each call consumes one token, creates an XBOSS job, and persists the processing result, and it explicitly warns that the call is not a pure read-only operation despite being a preview. That is genuine context the annotations alone would not convey (readOnlyHint=false is now explained rather than merely asserted). However, some of this arrives buried in generic idempotency boilerplate rather than being cleanly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is correctly front-loaded and the core sentences are tight, but roughly half the text is generic idempotency boilerplate that is repeated in the schema and includes clearly off-target lines such as 'not available to anonymous taste calls'. The mixed Korean/English register and the dangling token/job paragraph further obscure the main point.

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?

With no output schema, the description carries the burden of explaining what a preview returns, and it only says the full set of submit targets is shown, without describing the shape or fields of that listing. The preconditions, rejection modes, and handoff to 'submit' are well covered, so the gap is limited to return-value detail.

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 the schema already explains source_job_id, account_link_id, and expected_snapshot_hash, including the 409 rejection behavior. The description adds only the lineage detail that 'submit' takes this step's job_id as source_job_id, which is a marginal but real increment over the schema.

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?

The description uses a specific verb-plus-resource: it shows the full set of withholding-tax filing targets to submit from a job whose conversion and content validation have completed. It also explicitly contrasts itself with the sibling 'submit', which consumes this step's job_id as source_job_id, so the agent can distinguish the two without opening a 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?

It states a prerequisite (a prior hometax__session__login call with the same account_link_id) and the exact conditions under which the call is rejected: conversion not finished, or no normally converted targets. It also explains the handoff to 'submit' and the snapshot-match condition that governs it, leaving little to inference.

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