XBOSS

납부 내역 조회

hometax__tax__payment_statement__search

REQUIRES prior hometax__session__login call with same account_link_id. Search tax payment statement. mate_knd_cd: document type code. sbms_ym_strt/sbms_ym_end: submission year-month YYYYMM. 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": {
      "mate_knd_cd": "<mate_knd_cd>",
      "sbms_ym_strt": "<sbms_ym_strt>",
      "sbms_ym_end": "<sbms_ym_end>"
    },
    "name": "hometax__tax__payment_statement__search"
  }
}

Input Schema

Name	Required	Description
`attr_yr`	No	귀속연도 YYYY. 과세연월 시작과 종료를 입력하지 않고 이 값만 입력하면 그 해 1월부터 12월로 조회합니다.
`rcat_no`	No	접수번호. 그 접수 한 건만 찾을 때 입력합니다.
`bman_bsno`	No	사업자등록번호 숫자 10자리. 하이픈을 함께 입력해도 됩니다. 그 사업자의 건만 찾을 때 입력합니다.
`mate_knd_cd`	Yes	Document type code (자료종류코드) — one of: A0051 근로소득 지급명세서 / A0053 퇴직소득 지급명세서 / A0056 의료비 명세서 / A0057 기부금 명세서 / A0086 사업소득 지급명세서 / A0085 사업소득(연말정산용) 지급명세서 / A0088 기타소득 지급명세서 / A0087 종교인소득(연말정산용) 지급명세서 / A0084 이자·배당소득 지급명세서 / A0283 연금계좌 지급명세서 / A0055 비거주자 사업·기타소득 지급명세서 / A0259 부동산등 양도소득 지급명세서 / A0257 유가증권 양도소득 지급명세서. Any other value is refused before the NTS is contacted.
`sbms_ym_end`	Yes	Submission end year-month YYYYMM
`txtn_ym_end`	No	과세연월 종료 YYYYMM. 입력하지 않으면 과세연월로 좁히지 않습니다.
`sbms_ym_strt`	Yes	Submission start year-month YYYYMM
`txtn_ym_strt`	No	과세연월 시작 YYYYMM. 입력하지 않으면 과세연월로 좁히지 않습니다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

This is the strongest part: the description explains that each call consumes one token, creates an XBOSS task and stores the result, and explicitly warns that despite being a lookup it is NOT purely read-only — which substantiates the readOnlyHint=false annotation rather than contradicting it. It adds idempotency-key lifecycle rules (generate before first request, reuse only to recover a lost response) that go beyond the annotations. It does not describe the response shape or result limits, keeping it below 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 and purpose are front-loaded, but the description drifts into mixed English/Korean boilerplate, an apparently mistyped phrase ("taste calls"), and a vague closing sentence about provider data changes following per-tool procedures that conveys little. Roughly a third of the text is filler or redundant with the schema.

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?

For a 10-parameter search with no output schema, the description covers authentication, cost, side effects and idempotency well. It never says what is returned — result fields, row limits, or pagination — which is the main gap given there is no output schema to fall back on.

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%, so the schema already documents all ten parameters, including the enum of Korean document-type codes and the YYYYMM formats. The description restates mate_knd_cd and sbms_ym_strt/sbms_ym_end and adds the useful idempotency-key reuse semantics, but it contributes nothing about attr_yr, rcat_no, bman_bsno, txtn_ym_*, or account_link_id beyond the schema. Baseline 3 fits.

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?

"Search tax payment statement" states a specific verb and resource, and the required document-type/period parameters make the scope concrete. It does not explicitly distinguish itself from look-alike siblings such as hometax__tax__refund__search_detail or the wetax local payment history tools, so differentiation is left to the caller.

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?

A hard prerequisite is stated clearly ("REQUIRES prior hometax__session__login call with same account_link_id"), which is genuinely useful context. However there is no guidance on when to choose this tool over the many sibling search tools, and no exclusions or failure conditions beyond the idempotency note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?