XBOSS

근로복지공단 개인별 부과고지보험료 상세

comwel__info__individual_billed_premium__detail

Read-only

REQUIRES prior comwel__auth__npki_session__login call with same account_link_id. Fetch COMWEL individual billed-premium detail for a selected worker. 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
`insurance_year`	Yes	Insurance year YYYY
`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).
`insurance_month`	No	Insurance month MM
`worker_record_no`	Yes	Worker record number returned by worker_select
`labor_provider_yn`	Yes	Labor provider flag Y/N (from worker_select)
`worker_resident_no`	Yes	Worker resident number returned by worker_select
`refund_reflection_yn`	No	Refund reflection flag Y/N
`business_management_no`	No	Business management number
`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 19, 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?

Adds real context beyond the readOnly annotation: xlsx artifacts with a download_url valid 15 minutes, 7-day file retention, a recovery path via xdata__job__result with private recovery_receipt, and a per-call token cost of 1. The idempotency and receipt guidance is partly generic family boilerplate (and the 'anonymous taste calls' wording is confusing for an auth-required tool), but the artifact and retention behavior is genuinely useful.

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 text is long and dominated by protocol boilerplate about receipts, signing up, and key reuse that is at best tangential to a single-worker premium lookup. The actual purpose arrives after a capitalized prerequisite line, and the receipt/lane guidance muddies focus.

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 10 params fully documented, no output schema, and readOnly annotations, the description covers the essentials: auth prerequisite, file generation via artifacts[], and how to recover expired links. A short note on what the premium detail payload contains would have closed the remaining gap.

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 10 parameters including worker_resident_no, labor_provider_yn and request_idempotency_key are self-documented. The description only echoes output_formats/artifacts and the idempotency key usage, adding little that the schema does not already supply; 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: 'Fetch COMWEL individual billed-premium detail for a selected worker.' The 'selected worker' phrasing implicitly separates it from the sibling worker_select step, but the prerequisite sentence leads and the core purpose is buried mid-text rather than front-loaded.

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?

Gives a clear prerequisite ('REQUIRES prior comwel__auth__npki_session__login call with same account_link_id') and implies the worker_* params come from worker_select. However, it never names alternatives or a when-not condition, and no sibling tool such as premium_billing_notice__detail is contrasted despite overlapping domain.

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?