XBOSS

고지 내역 조회

hometax__tax__notice__search_history

REQUIRES prior hometax__session__login call with same account_link_id. Search tax notice history. Use strt_dt/end_dt (YYYYMMDD). The NTS accepts start dates within the last 10 years. 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소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Input Schema

Name	Required	Description
`end_dt`	Yes	End date YYYYMMDD
`strt_dt`	Yes	Start date YYYYMMDD
`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"
+}

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / ntpl_crp_cl_cd

Added value: +{
+  "description": "Taxpayer classification code (납세자 구분). Optional.",
+  "type": "string"
+}

addedInput schema / properties / surv_ttl

Added value: +{
+  "description": "Survey title filter (조회 제목). Optional.",
+  "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

A3.5/5.0

Behavior4/5

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

Annotations say readOnlyHint=false, and the description usefully explains why: the call creates an XBOSS job and stores its result, consumes one token per call, and is explicitly 'not purely read-only' regardless of the agency lookup. It also discloses artifact behavior (xlsx only when requested, artifacts[] with a download_url valid 15 minutes, files retained 7 days) and the recovery path via xdata__job__result. The recovery_receipt and idempotency passages, while verbose, do add real operational context.

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?

It's a long mixed-language wall of text in which a generic privacy/idempotency boilerplate block (recovery receipt, anonymous results, lane access) dominates and the actual purpose is one short sentence in the middle. The prerequisite is front-loaded, but the essential usage facts are scattered rather than structured.

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 9-parameter search with no output schema, it covers prerequisites, date constraints, file output, retention and error recovery, which is adequate. It never says what a notice record actually contains or how page_num/page_size interact with large result sets, which the agent still needs to call this well.

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 already 100%, so the baseline is 3, but the description adds a genuine constraint not in the schema: the NTS only accepts start dates within the last 10 years. It also ties output_formats to artifact generation and notes that idempotency_key is a distinct field from any provider-specific key.

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 second sentence, 'Search tax notice history,' gives a specific verb and resource, and the required strt_dt/end_dt pair narrows it to a date-ranged history lookup. However, it never distinguishes this from the many sibling history searches (overdue, cash receipt, payment statement), and the purpose statement is buried after an authentication prerequisite sentence.

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?

It states a hard prerequisite (prior hometax__session__login with the same account_link_id) and constraint (NTS accepts start dates within the last 10 years), plus conditional guidance for output_formats and idempotency key reuse. What is missing is any when-to-use/when-not guidance versus the dozens of other hometax search tools, so the agent must infer selection from the name alone.

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?