Skip to main content
Glama

홈택스 원천세 수정신고 제출 전 미리보기

hometax__tax__withholding__amendment_report__preview

REQUIRES prior hometax__session__login call with same account_link_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__amendment_report__preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_job_idYes이어서 진행할 이전 단계 작업의 job_id 를 그대로 입력합니다(job_ 으로 시작하는 작업 번호). 검토(review) 결과를 받고, 다시 볼 때는 미리보기(preview) 결과도 받습니다. 같은 조직과 환경, 같은 기관 연결에서 이 신고 유형으로 성공한 작업이어야 하고 아니면 진행하지 않고 거절하며, 받지 않는 작성 상태의 결과이면 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

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description adds real operational context: each call consumes one token ("호출마다 토큰 1소진"), creates an XBOSS job and persists its result, and explicitly warns "이 호출은 순수 읽기 전용이 아닙니다" — which reconciles the seemingly odd readOnlyHint=false for a preview tool. It also states no submission occurs, so the agent knows the report is not filed.

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 critical prerequisite is correctly front-loaded, but the idempotency guidance is restated four times across the paragraph and much of it is generic template filler that would apply to any tool. There is also a typo ("anonymous taste calls") and a vague trailing sentence ("기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다") that adds no actionable information.

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 non-mutating-but-not-read-only tool with full schema coverage and no output schema, the description covers prerequisites, side effects, cost, and the non-submission guarantee, and sketches what is returned ("전체 모습을 그대로"). The only meaningful gap is the relationship to __review and the stage ordering, which is left to the schema.

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 description coverage is 100%, so the baseline is 3; the description exceeds it by explaining idempotency-key semantics — generate before first request, reuse only to recover a lost response, new key for a new execution, unavailable to anonymous calls, and do not confuse it with a provider-specific idempotency_key field. That is meaning genuinely absent from the schema's one-line property description.

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?

"제출 직전 원천세 수정신고서 전체 모습을 그대로 보여 줍니다. 제출하지 않습니다." states a specific verb (preview/show) and resource (amendment report), and explicitly negates submission, which separates it from the sibling __submit and aligns with __review. The purpose is somewhat buried after the auth prerequisite and mixed-language boilerplate, so it is clear but not maximally front-loaded.

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?

"REQUIRES prior hometax__session__login call with same account_link_id" gives a hard prerequisite, and "제출 직전" implies the moment to use it. However, it never contrasts preview with the sibling __review or __lookup, nor states when not to call it — the agent must infer the stage ordering from the source_job_id schema rather than from 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