XBOSS

수신문서 일괄 상세 조회

nhis_edi__hr_payroll__received_documents__batch_details

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get batch details of received documents. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "row_indexes": "<row_indexes>"
    },
    "name": "nhis_edi__hr_payroll__received_documents__batch_details"
  }
}

Input Schema

Name	Required	Description
`to_date`	No	To date YYYYMMDD (default: today)
`form_name`	No	Form name filter
`from_date`	No	From date YYYYMMDD (default: 3 months ago)
`goji_round`	No	Notice round (고지 차수)
`row_indexes`	Yes	List of row indexes to fetch batch details for
`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).
`document_status`	No	Document status filter
`notice_year_month`	No	Notice year-month YYYYMM
`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?

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that each call consumes one token, creates an XBOSS task and stores its result, and explicitly warns the call is not purely read-only — consistent with readOnlyHint=false. That is real behavioral context an agent could not get from the structured fields. Minor deduction for the garbled "anonymous taste calls" clause, which muddies rather than clarifies.

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 front-loaded, which is good, but the idempotency paragraph occupies roughly half the text for a secondary optional parameter, while the actual batch semantics get one sentence. Mixed Korean/English and the untranslated "taste calls" fragment add noise.

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 9 parameters and no output schema, the description should at least say how row_indexes are obtained and what the batch response contains per row. It covers authentication and idempotency thoroughly but leaves the core data contract implicit.

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 baseline would be 3, but the schema's own request_idempotency_key entry just says "see the tool description," and the description does the work: new key per execution, reuse only for recovery after a lost response, and a note that a provider-specific idempotency_key is a different field. That is genuine added meaning. The required row_indexes parameter, however, gets no explanation of its source.

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 batch details of received documents" gives a clear verb and resource, and the batch framing is distinguishable in principle. However, it never contrasts this with the sibling nhis_edi__hr_payroll__received_documents__detail (single) or received_documents__options, so an agent must infer the split from the names alone.

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 states one hard prerequisite (a prior nhis_edi__session__login with the same account_link_id) and gives detailed rules for when to reuse vs. regenerate the idempotency key. What it does not give is when to choose this batch tool over the singular detail tool, or where the row_indexes values come from.

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?