Skip to main content
Glama

지급명세서 제출내역 조회

hometax__tax__payment_statement__search_submit_history

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 일용근로소득 지급명세서, 간이지급명세서 같은 지급명세서의 제출 내역을 제출 여부와 연월까지 조회합니다. sbms_ym_strt/sbms_ym_end 는 YYYYMM 형식입니다. 로그인한 호출이면 첫 요청 전에 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": {
      "sbms_ym_strt": "<sbms_ym_strt>",
      "sbms_ym_end": "<sbms_ym_end>"
    },
    "name": "hometax__tax__payment_statement__search_submit_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_numNoPage number (default 1)
page_sizeNoPage size (default 10)
mate_knd_cdNo자료종류코드(document type) - 비우면 그 달 제출분 전체: A0161=일용근로소득 간이지급명세서, A0162=연말정산 간이지급명세서, F0025=사업장제공자 등 과세자료 제출명세서, F0026=일용근로소득 지급명세서. Optional.
sbms_ym_endYesSubmission end year-month YYYYMM
txtn_ym_endNoTaxation end year-month YYYYMM
sbms_ym_strtYesSubmission start year-month YYYYMM
txpr_dscm_noNoTaxpayer number (hyphens allowed)
txtn_ym_strtNoTaxation start year-month YYYYMM
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

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, and the description correctly reinforces that with substance: each call consumes one token, creates an XBOSS job, and persists the processing result, and the tool is explicitly not purely read-only even though the agency-side lookup is a read. That is real behavioral context beyond the structured fields. The long idempotency-retry paragraph is useful but verbose and slightly tangled, which keeps it from a 5.

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 prerequisite is front-loaded and the purpose sentence follows cleanly, but the middle section on idempotency is a dense run of clauses mixing retry semantics, trial-mode restrictions, and field-name disambiguation. Several sentences could be compressed or split without losing content.

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 10-parameter read-oriented tool with no output schema, the description covers the prerequisite login, the date format, the cost, the side effect of job creation and result persistence, and the idempotency contract. Return-value shape is not described, but with no output schema that is the main remaining gap and it is a modest one.

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 baseline is 3, but the description adds meaning: it fixes sbms_ym_strt/sbms_ym_end to YYYYMM, explains the retry-only semantics of request_idempotency_key (reuse only to recover an unanswered request, always a fresh value for new runs), and warns that the agency-side idempotency_key field is a different field. Those are non-obvious constraints the schema alone defers to the description for.

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 states a specific verb and resource: it retrieves the submission history (제출 내역) of withholding payment statements such as 일용근로소득 지급명세서 and 간이지급명세서, down to submission status and year-month. That is clearly distinct from the sibling submit tools. It does not name hometax__tax__payment_statement__search as the non-history alternative, so there is no explicit sibling differentiation.

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 explicit sequencing guidance by naming hometax__session__login as the tool to call first with the same account_link_id, and it notes the account-less trial path cannot use the idempotency field. What is missing is any statement about when to prefer this over the plain payment_statement__search sibling, so the agent must infer the boundary.

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