XBOSS

수신문서 상세 조회

nhis_edi__hr_payroll__received_documents__detail

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get detailed info of a received document. 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__received_documents__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.6/5.0

Behavior4/5

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

Strong beyond-annotation disclosure: one token is consumed per call, the request creates and stores an XBOSS task, and the call is explicitly not purely read-only regardless of whether the source institution is queried. This is consistent with readOnlyHint=false and destructiveHint=false, and clarifies why a lookup mutates server state, though the persistence/duration of the XBOSS result is not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The leading REQUIRES clause and the purpose sentence are front-loaded before the idempotency detail, which is the right ordering. The idempotency paragraph runs five sentences and restates mechanics the schema description already points to, and the mixed Korean/English block reads as appended rather than integrated.

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?

With 8 all-optional parameters and no output schema, the definition covers auth, idempotency, and side effects well, but leaves a real gap: which subset of identifying parameters is required in practice and what the returned document detail contains. For a lookup with zero required params this should give more selection guidance.

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 baseline is 3. The description adds real meaning for request_idempotency_key (same-argument reuse for lost-response recovery, new key for new executions, unavailable to anonymous calls) and for the account_link_id prerequisite, but says nothing about how row_key, row_index, goji_round, or the *_text_contains filters combine to identify a document.

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?

"Get detailed info of a received document" states a specific verb and resource, and the Korean note clarifies that the call also creates an XBOSS task. It does not distinguish itself from close siblings such as received_documents__batch_details, received_documents__options, or document_box__sent_documents__detail, so the agent must infer which detail endpoint applies.

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?

It gives a hard precondition (prior nhis_edi__session__login with the same account_link_id) and a fairly detailed rule for when to reuse vs. regenerate request_idempotency_key. However, it never says when to choose this tool over the sibling batch/options/sent-document tools, nor that a list call must precede it to obtain row_key/row_index.

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?