XBOSS

증명서 다운로드

hometax__certificate__download

Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Download an issued certificate as PDF. Result: the issuance ids in data (cva_id, rcat_no) and the PDF in artifacts[] with a signed download_url. Get cva_id/rcat_no from the certificate application result (hometax__certificate__apply_auto or apply_with_template). Files: the document the institution issued, unchanged, as PDF, 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. 호출마다 토큰 1소진

Input Schema

Name	Required	Description
`cva_id`	Yes	Certificate ID (증명서 ID, cvaId)
`end_dt`	No	Issued-certificate list lookup end date YYYYMMDD. Optional.
`confirm`	No	Set true ONLY after showing the preview to the user and receiving their explicit approval. Omit it on the first call to obtain the preview. Printing consumes one issued copy and cannot be undone.
`rcat_no`	Yes	Receipt number (접수번호, rcatNo)
`strt_dt`	No	Issued-certificate list lookup start date YYYYMMDD. Optional — used when cva_id/rcat_no must be resolved from the list; the default window is the last 3 days.
`page_num`	No	Page number (default 1)
`page_size`	No	Page size (default 10)
`rpt_pkg_pth`	No	Report package path (rptPkgPth). Optional — looked up from the certificate list when omitted.
`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).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

changedInput schema / properties / page_num / description

Previous value: -"Issued-certificate list page number (1-based). Optional, default 1."New value: +"Page number (default 1)"

changedInput schema / properties / page_size / description

Previous value: -"Issued-certificate list page size. Optional, default 10."New value: +"Page size (default 10)"

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / end_dt

Added value: +{
+  "description": "Issued-certificate list lookup end date YYYYMMDD. Optional.",
+  "type": "string"
+}

addedInput schema / properties / page_num

Added value: +{
+  "description": "Issued-certificate list page number (1-based). Optional, default 1.",
+  "type": "integer"
+}

addedInput schema / properties / page_size

Added value: +{
+  "description": "Issued-certificate list page size. Optional, default 10.",
+  "type": "integer"
+}

addedInput schema / properties / strt_dt

Added value: +{
+  "description": "Issued-certificate list lookup start date YYYYMMDD. Optional — used when cva_id/rcat_no must be resolved from the list; the default window is the last 3 days.",
+  "type": "string"
+}

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "Set true ONLY after showing the preview to the user and receiving their explicit approval. Omit it on the first call to obtain the preview. Printing consumes one issued copy and cannot be undone.",
+  "type": "boolean"
+}

First observedSep 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, it discloses per-call token cost, that download_url lives 15 minutes, that files are retained 7 days, and how to refresh links. It does not itself state that the download consumes one issued copy irreversibly (that appears only in the confirm parameter's schema text), so the destructiveHint=true rationale is only indirectly explained.

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 result shape are correctly front-loaded, but the long middle block about recovery_receipt for anonymous results reads as cross-cutting boilerplate rather than anything specific to downloading a certificate. A trailing Korean token-cost note also feels appended rather than integrated.

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?

With no output schema, the description usefully describes the return shape (ids in data, PDF in artifacts[] with a signed URL) and link/retention lifetimes. All an agent needs to call correctly is present, though the destructive 'consumes an issued copy' semantics live only in the schema.

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 baseline is 3; the description earns a bump by explaining the origin of cva_id/rcat_no (the application result) rather than just their type. Other parameters (strt_dt, confirm, page_num) are left entirely to the schema.

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?

States a specific verb and resource (download an issued certificate as PDF) and names the upstream tools that produce the required ids (apply_auto, apply_with_template). An agent can tell this apart from application/list siblings without opening a schema.

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?

Explicitly states the prerequisite (prior hometax__session__login with the same account_link_id) and where to obtain cva_id/rcat_no. It also routes expired links to xdata__job__result, but never mentions the very close sibling hometax__certificate__apply_auto_download or when to use hometax__certificate__list instead.

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?