XBOSS

피부양자 자격신고 초기화

fourinsure__b1__member_qualification__dependent_init

REQUIRES prior fourinsure__session__login call with same account_link_id. Initialize dependent qualification 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__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

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, but the description adds real value beyond them: one token consumed per call, an XBOSS task is created and its result stored, and it explicitly states the call is not pure read-only even when the source lookup is a read. The idempotency-recovery behavior (lost response vs. new execution) is also disclosed.

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 login prerequisite is correctly front-loaded, but the idempotency paragraph is padded ('Without it, calling again remains a new request' restates the prior sentence) and the trailing Korean boilerplate about provider data changes is generic across the tool family rather than specific to this call.

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?

Prerequisite, cost, and side effects are covered, which is the important part for a non-read-only init tool with no output schema. What the initialization yields and which tool the agent should call next are not stated, leaving the workflow incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description does carry the semantic load for request_idempotency_key (the schema defers to it with 'see the tool description'), explaining generate-before-first-request and reuse-only-for-recovery, but adds nothing about account_link_id beyond what the schema already says.

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 ('Initialize dependent qualification declaration'), and the 'dependent' qualifier plus the sibling family (acqs/chg/los) makes the domain clear. What 'initialize' concretely produces is left abstract, so an agent knows the topic but not the artifact.

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 explicit ('REQUIRES prior fourinsure__session__login call with same account_link_id'), and the idempotency reuse policy is spelled out. However, nothing routes the agent between this and the adjacent dependent_draft_validate or nhis_edi__qualification__dependent__init, and no when-not condition is given.

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?