XBOSS

연말정산 건강보험 상세 조회

nhis_edi__hr_payroll__year_end_settlement__detail

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get year-end settlement health insurance detail. 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__hr_payroll__year_end_settlement__detail"
  }
}

Input Schema

Name	Required	Description
`row_key`	No	Stable row key from prior list
`row_index`	No	Row index the prior list returned for the chosen row - echo that value back as-is (not necessarily 0-based; e.g. NPS rows are 1-based rnum)
`goji_round`	No	Notice round (고지 차수)
`account_link_id`	No	Account link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
`notice_year_month`	No	Notice year-month YYYYMM
`row_text_contains`	No	Partial row text match
`cell_text_contains`	No	Partial cell text match
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=false; the description adds real context: one token is consumed per call, an XBOSS job is created and results are stored, and the call is explicitly not purely read-only regardless of whether the institution's source data was queried. That explains the readOnlyHint=false rather than contradicting it. It still leaves vague what an XBOSS job is and whether repeat calls have lingering effects.

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 body is dominated by generic cross-tool idempotency boilerplate and mixes English with Korean, diluting the single sentence that states the actual purpose. Sentences like "This optional key is not available to anonymous taste calls" add bulk without helping the target caller.

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?

For an 8-parameter, no-output-schema tool, the description covers prerequisites, token cost, and side effects well, but never says what the returned detail contains or how the identifying parameters (row_key, row_index, notice_year_month, goji_round) relate to a prior list. An agent knows how to call it safely but not what it will get back.

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 the eight parameters are already documented and the baseline is 3. The description does add genuine semantics for request_idempotency_key (reuse vs. new key, and that a provider-specific idempotency_key is a different field), but that is the only parameter it enriches.

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 second sentence gives a concrete verb and resource: "Get year-end settlement health insurance detail." That is specific enough to act on, but it offers no differentiation from near-siblings such as health_premiums__employee_details or premium_notices__detail, so an agent cannot tell from the text alone which one returns the year-end settlement view.

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 states a hard prerequisite (prior nhis_edi__session__login with the same account_link_id) and gives explicit when-to-reuse rules for request_idempotency_key: reuse only to recover a lost response, new key for a new execution. It does not say when to choose this tool over the sibling premium/detail tools, which keeps it below 5.

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?