XBOSS

발송문서 상세 조회

nhis_edi__document_box__sent_documents__detail

REQUIRES prior nhis_edi__session__login call with same account_link_id. 보낸문서 목록의 행 번호나 행 키로 고른 4대보험 기준소득월액, 보수월액, 월평균보수 변경신청서 한 건의 대상자와 보험별 신고 내용을 받습니다. 다른 서식의 문서는 오류로 돌아옵니다. 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__document_box__sent_documents__detail"
  }
}

Input Schema

Name	Required	Description
`row_key`	No	Row key returned by the list result; pass it back to select that row.
`firm_sym`	No	Workplace symbol (사업장기호) from the list result; pass through.
`efirm_sym`	No	Electronic workplace symbol from the list result; pass through.
`form_code`	No	Form code from the list result; pass through to pick the form/row.
`row_index`	No	Zero-based index of the row chosen from the list result.
`wrt_chasu`	No	Write sequence (작성차수) from the list result; pass through.
`wrt_dup_seq`	No	Write duplicate sequence from the list result; pass through.
`unit_firm_sym`	No	Unit workplace symbol from the list result; pass through.
`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?

With readOnlyHint=false already declared, the description goes further and explains why: each call consumes one token, creates an XBOSS job and stores the processing result, and is explicitly 'not purely read-only' regardless of whether the agency source is queried. It also discloses the idempotency contract (generate a key, reuse only for lost-response recovery, new key for new executions) and the form-mismatch error behavior. This is substantial disclosure beyond the annotations and is consistent with them.

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 correctly front-loaded, but the body mixes Korean and English and carries long generic idempotency boilerplate (including a reference to anonymous 'taste calls' that is irrelevant here) that dilutes the core instruction. The essential facts — one document, selected by row, this form only, not free/read-only — are present but scattered across the paragraph.

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?

There is no output schema, and the description compensates by naming what comes back (대상자 and per-insurance 신고 내용) along with the failure mode for other forms. Combined with the login prerequisite, token cost, and idempotency rules, an agent has enough to invoke it correctly. The only gap is that it does not state what a row-key mismatch or expired list session looks like.

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 schema already documents all ten parameters, setting the baseline at 3. The description adds genuine meaning on top: row_index/row_key are framed as the two ways to select a single row from the list result, account_link_id is tied to the login prerequisite, and request_idempotency_key gets an explicit reuse policy and a warning not to confuse it with provider-specific idempotency_key. That extra selection and key-handling context lifts it above baseline.

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 description states a specific verb and resource: retrieve one sent document (4대보험 기준소득월액/보수월액/월평균보수 변경신청서) selected by row index or row key, returning the subject and per-insurance report contents. It also bounds the scope by noting other form types return an error, which distinguishes it from the sibling list tool. The purpose is clear but is embedded mid-sentence in a long bilingual block rather than front-loaded.

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 gives a hard prerequisite (prior nhis_edi__session__login with the same account_link_id) and implies the selection flow by requiring row_index/row_key taken from the sent-documents list result. It also excludes wrong inputs by warning that documents of other forms return an error. It stops short of explicitly naming the list tool as the required predecessor or describing what to do when a row is stale.

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?