Skip to main content
Glama

수신문서 일괄 상세 조회

nhis_edi__hr_payroll__received_documents__batch_details

REQUIRES prior nhis_edi__session__login call with same account_link_id. 보수월액 수신문서 목록 조회가 돌려준 행 번호를 넣으면 행마다 상세를 열어 결과 목록으로 받습니다. 한 건이라도 못 열면 결과 전체의 성공 표시가 꺼지고 안내 문장이 붙습니다. 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

NameRequiredDescriptionDefault
to_dateNoTo date YYYYMMDD (default: today)
form_nameNoForm name filter
from_dateNoFrom date YYYYMMDD (default: 3 months ago)
goji_roundNoNotice round (고지 차수)
row_indexesYesList of row indexes to fetch batch details for
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
document_statusNoDocument status filter
notice_year_monthNoNotice year-month YYYYMM
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses substantial behavior: each call consumes one token, it creates an XBOSS task and stores results, it is explicitly not purely read-only despite querying institution data, and any single failure flips the whole result's success flag with an appended guidance sentence. It also details idempotency-key semantics for recovery vs new execution.

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 idempotency paragraph is verbose and the Korean/English mixing makes it harder to scan. Several sentences could be tightened without losing information.

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?

For a 9-parameter tool with no output schema, the description covers prerequisites, partial-failure semantics, token cost, side effects, and idempotency. It is nearly complete; only explicit contrast with the single-detail sibling is missing.

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 is 3, but the description adds real meaning: row_indexes must come from the list tool's returned row numbers, and the idempotency key's reuse rules are explained. This goes beyond the schema's field descriptions.

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 operation: it takes row indexes returned by the received-documents list lookup and opens a detail per row, returning a result list. This distinguishes it from the single-document detail sibling and the list tool. The mixed Korean/English phrasing slightly obscures the core statement, keeping it from a 5.

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 clear prerequisite (prior nhis_edi__session__login with the same account_link_id) and explains the input source (row numbers from the list lookup). It does not explicitly contrast with the single-detail sibling, but the batch-vs-single distinction is implied by '행마다'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources