XBOSS

자격상실 신고(초기화)

nhis_edi__qualification__loss__init

REQUIRES prior nhis_edi__session__login call with same account_link_id. 자격 상실 신고서의 보험별 상실일과 상실 코드 칸, 보수총액, 이직확인서 칸과 목록 이름을 로그인한 연동 계정으로 받습니다. 칸 구성은 저장해 둔 상실 신고서 화면 정보에서 읽습니다. 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소진 요청 처리 시 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__qualification__loss__init"
  }
}

Input Schema

Name	Required	Description	Default
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description goes further by disclosing per-call token consumption ("호출마다 토큰 1소진"), that an XBOSS task is created and the result stored, and that the call is explicitly not purely read-only even when the agency source is only queried. It never says what server state is mutated by creating that task, which keeps it short of a 5.

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 is correctly front-loaded, but the definition is bilingual in a patchwork way and the idempotency block is five sentences with overlapping restatements ("Without it, calling again remains a new request" largely repeats the preceding sentence). Usable, but it could be cut by a third without losing meaning.

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 compensates by enumerating what is returned and where the field layout comes from (saved loss-report screen info), plus cost and side-effect information. Nothing essential for a correct first call appears missing, though the result shape after the XBOSS task runs is left undefined.

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 a 3 is the floor; the description earns more by explaining account_link_id must match the logged-in linked account ("로그인한 연동 계정으로 받습니다") and by carrying the entire idempotency-key semantics the schema defers to it. It also warns that a provider-specific idempotency_key is a different field, preventing a likely confusion.

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?

The description names the specific resource (자격 상실 신고서 / qualification-loss report) and enumerates the concrete fields it returns to the caller (per-insurance loss date, loss code, total remuneration, employment-confirmation fields and list names), so it is distinguishable from the acquisition/change/dependent siblings. The verb is only implied via "받습니다" (receives) plus the title's "초기화"; an agent must infer that this initializes/prefills a loss report rather than submitting one.

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?

"REQUIRES prior nhis_edi__session__login call with same account_link_id" gives an explicit prerequisite, and the idempotency paragraph states exactly when to reuse a key (recover a lost response) versus mint a new one (new execution). It does not say when to prefer this over the sibling acquisition/change/dependent inits, so alternatives remain implicit.

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?