XBOSS

체납 내역 조회

hometax__tax__overdue__search_history

Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search overdue tax history (체납 내역). Narrow the period with strt_dt/end_dt; without them the NTS default period applies. Only 3 rows come back per page unless you raise page_size. 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`	No	End date YYYYMMDD or YYYY-MM-DD (optional)
`strt_dt`	No	Start date YYYYMMDD or YYYY-MM-DD (optional)
`page_num`	No	Page number (default 1)
`surv_ttl`	No	Survey title filter (조회 제목). Optional.
`page_size`	No	Page size (default 3)
`ntpl_crp_cl_cd`	No	Taxpayer classification code (납세자 구분). Optional.
`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"
+}

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

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses login requirements, default period behavior, default page size of 3, artifact generation with 15-minute download links and 7-day retention, recovery via xdata__job__result, anonymous receipt handling, idempotency key semantics, and per-call token cost. This is substantial behavioral context not present in the annotations.

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 description is a long, multi-topic block that mixes the search operation with generic file-retention, anonymous-receipt, and idempotency boilerplate. The core search guidance is front-loaded, but many sentences do not earn their place for a read-only history query.

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 9-parameter, no-output-schema search tool, it covers auth, pagination defaults, file artifacts, recovery, and cost, which is enough for correct invocation. It does not describe the shape of the returned overdue-history rows, so it is not fully complete.

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; the description adds operational meaning for strt_dt/end_dt (NTS default period), page_size (default 3), output_formats (xlsx only), account_link_id (must match the login call), and request_idempotency_key (generate/reuse rules). It leaves some schema-documented parameters such as surv_ttl and ntpl_crp_cl_cd unmentioned, so it is not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Search overdue tax history') and includes the Korean term, which clearly distinguishes it from sibling searches for notices, payment statements, or refunds. The login prerequisite is front-loaded without obscuring the core operation.

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 states the prerequisite login and matching account_link_id, explains how to narrow by strt_dt/end_dt and what happens when they are omitted, and notes page_size and output_formats conditions. It does not explicitly exclude or route to sibling tax-search tools, so it stops short of full when/when-not guidance.

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?