XBOSS

증명서 PDF 다운로드

fourinsure__b1__certificate__history__pdf_download

Destructive

REQUIRES prior fourinsure__session__login call with same account_link_id. Download certificate PDF. 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
`cvrc_no`	No	Receipt number (접수번호) selecting which certificate application to act on.
`dry_run`	No	Default true (preview): returns the receipt number, status and dates only. Set false together with confirm_download=true to receive the actual PDF in the result artifacts.
`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).
`confirm_download`	No	Default false. Set true together with dry_run=false to receive the actual PDF; otherwise the call previews only.
`download_all_available`	No	Default false. When true, acts on all printable applications instead of a single cvrc_no.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 24, 2026

addedInput schema / properties / confirm_download

Added value: +{
+  "description": "Default false. Set true together with dry_run=false to receive the actual PDF; otherwise the call previews only.",
+  "type": "boolean"
+}

addedInput schema / properties / cvrc_no

Added value: +{
+  "description": "Receipt number (접수번호) selecting which certificate application to act on.",
+  "type": "string"
+}

addedInput schema / properties / download_all_available

Added value: +{
+  "description": "Default false. When true, acts on all printable applications instead of a single cvrc_no.",
+  "type": "boolean"
+}

addedInput schema / properties / dry_run

Added value: +{
+  "description": "Default true (preview): returns the receipt number, status and dates only. Set false together with confirm_download=true to receive the actual PDF in the result artifacts.",
+  "type": "boolean"
+}

AddedOct 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Adds useful context beyond annotations: 15-minute download links, 7-day retention, token cost, and receipt semantics. However, annotations declare destructiveHint=true and readOnlyHint=false, and the description never explains any destructive behavior; a download reads as non-destructive, and the crucial detail that dry_run defaults to true (so no PDF is returned unless override) is absent.

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 sprawls into lengthy anonymous-recovery_receipt exposition (publishing, loss, signing in) that is largely tangential to invoking this specific download tool. Several sentences could be trimmed without loss to the agent's decision.

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?

With no output schema, the description usefully explains the returned artifacts[], download_url lifetime and retention. But for a destructiveHint tool with a default-preview dry_run schema, the omission of the preview-vs-download mechanics is a meaningful completeness gap for correct invocation.

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 description coverage is 100%, so all five parameters are already documented in the schema. The description adds no parameter-level meaning (e.g., dry_run/confirm_download pairing or download_all_available) beyond what the schema provides, so the baseline 3 applies.

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 specific verb and resource ('Download certificate PDF'), clearly distinct from the sibling history__detail and history__list tools. It does not, however, clarify that the default behavior is a preview rather than an actual download, which slightly blurs the purpose.

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 ('REQUIRES prior fourinsure__session__login call with same account_link_id') and names the alternative path ('If a link has expired, call xdata__job__result...'). It omits when to use the dry_run default vs the real download, leaving a usage gap.

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?