XBOSS

보험료 완납증명서 발급

nhis_edi__certificates__payment_completion__issue

Destructive

REQUIRES prior nhis_edi__session__login call with same account_link_id. Issue an NHIS payment-completion (완납증명서) or payment (납부확인서) certificate. IRREVERSIBLE: the certificate is issued at 건강보험공단 and an issue number is assigned; there is no cancel action. This writes to the institution. The first call is not executed: it returns a preview of exactly what will be sent and a one-time confirmation_token (error WRITE_CONFIRMATION_REQUIRED). Show that preview to the user as it is. Only after the user agrees, call again with the same arguments plus that confirmation_token. Never add the token without the user's agreement. Changing any argument makes the token invalid; call without the token to get a new preview. 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소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nhis_edi__certificates__payment_completion__issue"
  }
}

Input Schema

Name	Required	Description
`year`	No	Target year YYYY (payment_certificate only). Defaults to the current year.
`issue_gubun`	No	발급구분 00/01/02 (payment_certificate only). Default '00'.
`issue_usage`	No	발급용도 code. payment: 11/12/13, completion: 51/52. Default '11'.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`certificate_kind`	No	payment_certificate(납부확인서) or completion_certificate(완납증명서). Default payment_certificate.
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description goes well beyond them: it declares the issuance irreversible with no cancel action, that this writes to the institution, that each call consumes a token, and that files live 7 days with 15-minute download links. The recovery_receipt rules and the 'not purely read-only' note 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the precondition, then the irreversible-write warning, then the confirmation protocol, then file/result handling — a sensible order. It is long and the trailing Korean sentences partly restate the write/read-only point and the token cost already implied earlier, which is mild redundancy rather than confusion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a complex two-call, institution-writing flow, the description covers the preview/confirm cycle, artifact download and retention windows, and how to recover expired links or anonymous results. An agent has everything needed to call it correctly without further context.

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 meaning beyond the schema by explaining that confirmation_token is one-time, bound to the exact arguments, and invalidated by any change, and that a token-less call yields a fresh preview. Per-parameter meaning for year/issue_gubun/issue_usage is left to the schema, which already covers it.

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: 'Issue an NHIS payment-completion (완납증명서) or payment (납부확인서) certificate,' and names the certificate variants, so an agent knows exactly what artifact is produced and can distinguish it from informational NHIS tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions ('REQUIRES prior nhis_edi__session__login call with same account_link_id'), the two-step call protocol after WRITE_CONFIRMATION_REQUIRED, and the alternative to use for expired links (xdata__job__result with the job_id). It also states when not to add the token and what to do if arguments change.

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?