Skip to main content
Glama

홈택스 원천세 수정신고 신고 내역 조회

hometax__tax__withholding__amendment_report__history

먼저 호출할 도구: 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": {
      "business_no": "<business_no>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "hometax__tax__withholding__amendment_report__history"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes조회 기간의 종료일입니다. 형식은 start_date 와 같고 start_date 보다 빠를 수 없습니다.
page_numNo받을 쪽 번호입니다. 1부터 세는 정수이고 입력하지 않으면 1 입니다.
page_sizeNo한 쪽에 받을 신고 수입니다. 1 이상 100 이하의 정수이고 입력하지 않으면 10 입니다.
start_dateYes조회 기간의 시작일입니다. YYYYMMDD 여덟 자리의 실제 날짜로 입력하며 end_date 보다 늦으면 입력 오류로 거절합니다.
business_noYes신고 내역을 조회할 사업자의 사업자등록번호입니다. 하이픈 없이 숫자 10자리로 입력합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
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

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses a per-call token cost, that an XBOSS task is created and the processing result persisted, and explicitly warns that the call is NOT purely read-only despite reading institutional data — which explains and is consistent with readOnlyHint=false. It also fully specifies the idempotency-key recovery protocol (new value per new execution, same value+args only to recover an unanswered request) and warns not to confuse it with the institution-side idempotency_key field.

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?

Front-loading is good — the login prerequisite and the period-scoped purpose come first. But the text then hops across idempotency mechanics, sample-mode limitations, field disambiguation, token billing, task creation, and read-only status, and the closing line about institutional data changes following 'tool-specific execution contents and existing confirmation procedures' is vague boilerplate that does not earn its place.

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 7-parameter, no-output-schema tool this is fairly complete: authentication prerequisite, period scoping, result composition, pagination, and the idempotency protocol are all covered. What an agent still cannot predict is the shape of individual returned records (the report classification field it is told to filter on is never named as a field), though the absence of an output schema limits how much the description could reasonably carry.

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 schema already documents dates, business number, and paging, making 3 the baseline. The description adds real meaning on top: it ties account_link_id to the login call and, importantly, supplies the request_idempotency_key usage rules that the schema itself defers to the description ('쓰는 법은 도구 설명에 있습니다'), which is exactly the gap the description needed to close.

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 and resource: look up withholding tax report receipt history for a period. It also clarifies a non-obvious scope fact — that regular, amendment, and late-after-deadline filings all come back in one result, so amendment entries must be filtered out by report classification — which is what actually separates it from the sibling history tools. It stops short of naming those siblings explicitly.

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?

Gives a concrete prerequisite and sequencing rule ('먼저 호출할 도구: hometax__session__login (같은 account_link_id)'), plus post-call guidance to select the amendment records via the report classification field. It does not state when to prefer regular_report__history or late_report__history instead, so routing among the three history tools is left partly implicit.

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