Skip to main content
Glama

수신문서 상세 조회

nhis_edi__hr_payroll__received_documents__detail

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

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

NameRequiredDescriptionDefault
row_keyNo가장 최근 목록 결과의 행 키(예: row:3). 그 목록 안의 자리를 가리키며 문서의 고정 번호가 아닙니다. 다시 쓰기 전에 같은 기간과 조건으로 목록을 다시 조회해 주세요.
to_dateNo조회 종료일 YYYYMMDD. 입력하지 않으면 오늘입니다.
form_nameNo서식 이름으로 문서를 거릅니다.
from_dateNo조회 시작일 YYYYMMDD. 입력하지 않으면 3개월 전입니다.
row_indexNo앞선 목록 결과가 돌려준 그 행의 행 번호. 받은 값을 그대로 입력합니다(0 부터 세지 않을 수 있습니다. 예: 국민연금 행은 1 부터 세는 rnum 입니다).
goji_roundNo고지 차수.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
document_statusNo문서 상태로 문서를 거릅니다.
notice_year_monthNo고지 연월 YYYYMM.
row_text_containsNo행의 글자에 이 값이 들어 있는 행을 고릅니다.
cell_text_containsNo칸의 글자에 이 값이 들어 있는 행을 고릅니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / cell_text_contains / description
      Previous value: -"Partial cell text match"New value: +"칸의 글자에 이 값이 들어 있는 행을 고릅니다."
    • changedInput schema / properties / document_status / description
      Previous value: -"Document status filter"New value: +"문서 상태로 문서를 거릅니다."
    • changedInput schema / properties / form_name / description
      Previous value: -"Form name filter"New value: +"서식 이름으로 문서를 거릅니다."
    • changedInput schema / properties / from_date / description
      Previous value: -"From date YYYYMMDD (default: 3 months ago)"New value: +"조회 시작일 YYYYMMDD. 입력하지 않으면 3개월 전입니다."
    • changedInput schema / properties / goji_round / description
      Previous value: -"Notice round (고지 차수)"New value: +"고지 차수."
    • changedInput schema / properties / notice_year_month / description
      Previous value: -"Notice year-month YYYYMM"New value: +"고지 연월 YYYYMM."
    • changedInput schema / properties / row_index / description
      Previous value: -"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)"New value: +"앞선 목록 결과가 돌려준 그 행의 행 번호. 받은 값을 그대로 입력합니다(0 부터 세지 않을 수 있습니다. 예: 국민연금 행은 1 부터 세는 rnum 입니다)."
    • changedInput schema / properties / row_key / description
      Previous value: -"Row key from the most recent list result (for example row:3). It marks the row's position in that list, not a permanent document id - call the list again with the same period and filters before reusing it."New value: +"가장 최근 목록 결과의 행 키(예: row:3). 그 목록 안의 자리를 가리키며 문서의 고정 번호가 아닙니다. 다시 쓰기 전에 같은 기간과 조건으로 목록을 다시 조회해 주세요."
    • changedInput schema / properties / row_text_contains / description
      Previous value: -"Partial row text match"New value: +"행의 글자에 이 값이 들어 있는 행을 고릅니다."
    • changedInput schema / properties / to_date / description
      Previous value: -"To date YYYYMMDD (default: today)"New value: +"조회 종료일 YYYYMMDD. 입력하지 않으면 오늘입니다."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description goes further: it warns that each call consumes one token, that a XBOSS job is created and results are persisted, and that the call is not purely read-only even though the institutional source lookup is a read. That is behavior an agent could not infer from annotations. The value is diluted somewhat by boilerplate about provider-specific keys and 'anonymous taste calls', which does not appear relevant here.

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

Conciseness2/5

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

The useful content is front-loaded, but the description mixes Korean and English and spends several sentences on generic idempotency-key policy, plus mentions of token consumption and XBOSS job creation that could be tightened. Much of that wording is boilerplate that would be identical across many tools and does not help this specific call.

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 12-parameter, all-optional detail tool with no output schema, the description covers the prerequisite login, the fact that rows come from a prior list result, and the shape of what is returned, including the variation in tables by document type. Missing only minor points such as pagination or limits on the returned tables.

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% and every one of the 12 parameters carries its own description, including subtle semantics for row_key, row_index, and account_link_id. The description adds nothing about individual parameters beyond repeating the row-selection idea, so the schema does all the work; baseline 3 applies.

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 concrete verb and resource: it opens exactly one row picked from the received-document list and returns the document title, the institution's document code, and per-table columns and rows. It also notes that the tables differ by document type, which tells an agent what to expect. It does not differentiate itself from the sibling batch_details tool by name, so it stops short of 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 opens with a hard prerequisite (a prior nhis_edi__session__login call with the same account_link_id) and frames the use case as selecting a single row from a list result, which sets clear context. There are no explicit exclusions or named alternatives such as the batch-details sibling, so guidance is clear but not comprehensive.

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