XBOSS

피부양자 신고(초기화)

nhis_edi__qualification__dependent__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__dependent__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

A4.1/5.0

Behavior5/5

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

Goes well past the annotations: discloses a 1-token cost per call, that a XBOSS job is created and its result persisted, that the call is not purely read-only despite querying the institution source, and that retries without an idempotency key count as new requests. This is consistent with readOnlyHint=false and destructiveHint=false while adding material 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.

Conciseness3/5

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

The prerequisite and scope are correctly front-loaded, but the description is bloated: five consecutive sentences on idempotency, a boilerplate note about provider-specific keys, plus a hedged sentence on institutional data changes that adds little. The Korean/English mixing makes the payload harder to scan.

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 does at least name what comes back (the form sections and the acquisition/loss discriminator), and it covers auth, cost, side effects, and retry safety for a 2-parameter tool. Return-shape detail and per-field expectations remain thin.

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 earns an extra point by supplying the full semantics of request_idempotency_key (generate before first call, reuse only for recovery, new key per execution) that the schema only gestures at with 'see the tool description'. It also reinforces the account_link_id rule that the session login must use the same value.

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 Korean sentence names a concrete resource: the subscriber/dependent/disabled-and-veteran/foreigner section fields of the dependent acquisition-loss report form, plus the acquisition-vs-loss discriminator value. That is a specific verb+resource beyond the title, though the 'init' (form-initialization) aspect is only implied and nothing distinguishes it from acquisition__init or fourinsure__b1__member_qualification__dependent_init.

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?

It front-loads an explicit prerequisite ('REQUIRES prior nhis_edi__session__login call with same account_link_id') and gives detailed when/how guidance for the idempotency key (new execution vs. lost-response recovery, anonymous calls excluded). It stops short of stating when to pick this over the sibling dependent/acquisition/loss init tools.

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?