XBOSS

직원 자격변동 신고 초기화

fourinsure__b1__member_qualification__chg_init

REQUIRES prior fourinsure__session__login call with same account_link_id. Initialize employee qualification change declaration. 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": "fourinsure__b1__member_qualification__chg_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.6/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that each call consumes one token, creates an XBOSS task and persists the result, and that the call is not a pure read despite reading institution source data. It also explains the lost-response recovery semantics of the idempotency key, which is real behavioral context not present in structured fields.

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 front-loaded, which is good, but the idempotency-key guidance sprawls across four sentences with restatement ("Without it, calling again remains a new request"), and the mixed English/Korean text makes the core purpose harder to scan than it needs to be.

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

Completeness3/5

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

There is no output schema, yet the description never indicates what initialization yields (a draft handle, session context, or request key) or what the caller should do next with chg_draft_validate. Token cost and side effects are covered well, but the result contract for a two-step init flow is missing.

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 baseline is 3, but the description adds meaning: the idempotency key is optional, scoped to authenticated calls only, must be reused with identical arguments strictly for recovery, and must not be confused with a provider-specific idempotency_key field. It also ties account_link_id to the prior login call via "same account_link_id".

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?

"Initialize employee qualification change declaration" gives a specific verb (initialize) and a specific resource, and the chg_ prefix distinguishes it from the acqs_/dependent_/los_ siblings. What "initialize" actually produces is left implicit, so an agent knows the domain but not the concrete effect.

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?

The prerequisite is stated explicitly ("REQUIRES prior fourinsure__session__login call with same account_link_id"), which is genuinely useful selection context. However, there is no guidance on when to pick this over sibling entry points such as chg_draft_validate or the other *_init tools, and no exclusion or follow-on step is named.

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?