XBOSS

직원 자격상실 초안 저장

fourinsure__b1__member_qualification__los_save

Destructive

REQUIRES prior fourinsure__session__login call with same account_link_id. 자격상실 신고서를 정보연계센터에 초안으로 저장하고 접수번호를 받습니다. 기관에 실제로 남는 쓰기이고 이 API 로 되돌릴 수 없습니다. 신고서를 기관에 전송하지는 않으며, 마지막 전송은 사용자가 정보연계센터 화면에서 직접 합니다. confirm=true 없이 부르면 저장하지 않고 보낼 값을 미리 보여 주므로, 사용자에게 보여 주고 동의를 받은 뒤 confirm=true 로 다시 부르세요. rrkey 는 자격상실 가입자 조회 결과의 값을 넣습니다. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rrkey": "<rrkey>",
      "applicant_name": "<applicant_name>",
      "resident_registration_number": "<resident_registration_number>",
      "common_loss_date": "<common_loss_date>",
      "current_year_salary_amount": "<current_year_salary_amount>",
      "health_insurance_month_count": "<health_insurance_month_count>",
      "national_pension": "<national_pension>",
      "health_insurance": "<health_insurance>",
      "employment_insurance": "<employment_insurance>",
      "workers_compensation": "<workers_compensation>"
    },
    "name": "fourinsure__b1__member_qualification__los_save"
  }
}

Input Schema

Name	Required	Description
`rrkey`	Yes	Member rrkey from los_member_lookup.
`confirm`	No	Must be true to save. Default false.
`dry_run`	No	Assemble payload without posting save.
`applicant_name`	Yes	Member name in Korean.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`common_loss_date`	Yes	Common loss date YYYYMMDD.
`health_insurance`	Yes	건강보험 상실 사유. 코드와 이름을 둘 다 입력합니다. 비우면 저장하지 않습니다.
`national_pension`	Yes	국민연금 상실 사유. 코드와 이름을 둘 다 입력합니다. 비우면 저장하지 않습니다.
`employment_insurance`	Yes	고용보험 상실 사유. 코드와 이름을 둘 다 입력합니다. 비우면 저장하지 않습니다.
`workers_compensation`	Yes	산재보험 상실 사유. 코드와 이름을 둘 다 입력합니다. 비우면 저장하지 않습니다.
`current_year_salary_amount`	Yes	Current-year total wage.
`health_insurance_month_count`	Yes	NHI contribution month count.
`resident_registration_number`	Yes	13-digit resident registration number.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true): it says the write persists at the institution, cannot be reverted through this API, that the report is not transmitted to the agency (the user finishes on the center's screen), that each call consumes one token, and that an XBOSS job is created and its result stored. This is exactly the operational context an agent needs before an irreversible write.

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?

The auth requirement is front-loaded and the confirmation workflow is sequenced clearly. The closing sentences about the call not being pure read-only and about following each tool's existing confirmation procedures restate what destructiveHint already conveys, so a few lines do not fully earn their place.

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?

For a 13-parameter, nested-object mutation with no output schema, the description covers the essentials: authentication, the preview-then-confirm flow, irreversibility, and the returned receipt number. It does not describe failure or partial-save behavior when some insurance sections are empty, which is a meaningful gap for a multi-section write.

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 real meaning by stating that rrkey must come from the los_member_lookup result and by framing confirm as the gate that turns a preview into an actual save. It does not explain the dry_run/confirm interaction or how the four insurance reason objects relate to each other, which keeps it from a 5.

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: saves a 자격상실 (loss-of-coverage) report as a draft to the 정보연계센터 and returns a receipt number. The scope is clearly narrower than a final submission, which it explicitly disclaims. It does not name a sibling tool (e.g., los_draft_validate) as an alternative, so differentiation is implied rather than stated.

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?

Gives a concrete precondition (prior fourinsure__session__login with the same account_link_id) and an explicit two-step workflow: call without confirm to preview, show the user, obtain consent, then re-call with confirm=true. It does not route to sibling validation tools or state when not to use this tool, leaving the alternative path to inference.

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?