XBOSS

환급금 상세 조회

hometax__tax__refund__search_detail

Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search tax refund details. Use strt_dt/end_dt (YYYYMMDD). The NTS only serves the last 5 years from today. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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소진

Input Schema

Name	Required	Description
`end_dt`	Yes	End date YYYYMMDD
`strt_dt`	Yes	Start date YYYYMMDD
`txaa_id`	No	Tax accountant ID (txaa_yn='Y'일 때 필수)
`txaa_yn`	No	세무대리인 조회 여부 Y/N. 'Y'이면 txaa_id 와 txpr_dscm_no 가 함께 필요하고, 세무대리인은 지급완료('1') 건만 조회됩니다.
`page_num`	No	Page number (default 1)
`page_size`	No	Page size (default 10)
`inqr_cl_cd`	No	조회구분(payment status): '00'=전체, '1'=지급완료, '2'=미수령, '3'=1년경과 미수령. Optional.
`txpr_dscm_no`	No	Taxpayer number (hyphens allowed; 세무대리인 조회 시 필수)
`output_formats`	No	Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
`account_link_id`	No	Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / request_idempotency_key

Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / inqr_cl_cd / description

Previous value: -"Inquiry classification code"New value: +"조회구분(payment status): '00'=전체, '1'=지급완료, '2'=미수령, '3'=1년경과 미수령. Optional."

addedInput schema / properties / inqr_cl_cd / enum

Added value: +[
+  "00",
+  "1",
+  "2",
+  "3"
+]

changedInput schema / properties / txaa_id / description

Previous value: -"Tax accountant ID"New value: +"Tax accountant ID (txaa_yn='Y'일 때 필수)"

changedInput schema / properties / txaa_yn / description

Previous value: -"Tax accountant flag Y/N"New value: +"세무대리인 조회 여부 Y/N. 'Y'이면 txaa_id 와 txpr_dscm_no 가 함께 필요하고, 세무대리인은 지급완료('1') 건만 조회됩니다."

changedInput schema / properties / txpr_dscm_no / description

Previous value: -"Taxpayer number (hyphens allowed)"New value: +"Taxpayer number (hyphens allowed; 세무대리인 조회 시 필수)"

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / output_formats

Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

First observedSep 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnly/non-destructive annotations, it discloses the 5-year NTS retention limit, that file links live 15 minutes and files are kept 7 days, and the per-call token cost. Some of the receipt/idempotency boilerplate is only loosely relevant, but the useful behavioral context is substantial.

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 body is bloated with generic boilerplate about anonymous recovery_receipt and idempotency-key reuse that is largely irrelevant to a read-only refund search, diluting the essential 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?

Given no output schema, the description covers the key behaviors an agent needs: login prerequisite, retention window, file output format and expiry, and token cost. It is largely complete for invoking correctly, though return-field structure is only partially implied.

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 most parameters are already documented in the schema. The description adds meaning for the date window (5-year limit) and file output (artifacts[], download_url, retention) but says nothing about txaa_yn/txaa_id, inqr_cl_cd, or pagination beyond the schema.

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 clear verb+resource ('Search tax refund details') matching the title, and adds a distinguishing scope (date range, 5-year NTS window). It does not explicitly contrast with the similar sibling hometax__tax__unclaimed_refund__search, so it falls short of full 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?

Gives concrete preconditions (must call hometax__session__login first with the same account_link_id), plus when to use xdata__job__result for expired links and when to request files via output_formats. Lacks guidance on when to pick this over unclaimed_refund__search.

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?