Skip to main content
Glama

건강보험 고지 상세 조회

nhis_edi__hr_payroll__premium_notices__detail

먼저 호출할 도구: nhis_edi__session__login (같은 account_link_id). 탐색 결과의 행 키나 고지 연월과 문서 이름으로 고지내역서 하나를 열어 고지 연월과 차수, 보험 종류, 기관이 준 고지 항목 행을 받습니다. 항목 이름은 기관 코드 그대로 옵니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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__premium_notices__detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
row_keyNo목록 결과가 돌려준 행 키. 받은 값을 그대로 입력해 그 행을 고릅니다.
to_dateNo조회 종료일 YYYYMMDD.
from_dateNo조회 시작일 YYYYMMDD.
row_indexNo목록 결과에서 고른 행의 번호. 0 부터 셉니다.
goji_roundNo고지회차.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
notice_year_monthNo고지 연월 YYYYMM.
row_text_containsNo행 전체 글자에 이 값이 들어 있는 행을 고릅니다.
cell_text_containsNo칸의 글자에 이 값이 들어 있는 행을 고릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. Changed8 schema fields changed
    • changedInput schema / properties / cell_text_contains / description
      Previous value: -"Select the row whose cell text contains this string."New value: +"칸의 글자에 이 값이 들어 있는 행을 고릅니다."
    • changedInput schema / properties / from_date / description
      Previous value: -"Search range start date (YYYYMMDD)."New value: +"조회 시작일 YYYYMMDD."
    • 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: -"Zero-based index of the row chosen from the list result."New value: +"목록 결과에서 고른 행의 번호. 0 부터 셉니다."
    • changedInput schema / properties / row_key / description
      Previous value: -"Row key returned by the list result; pass it back to select that row."New value: +"목록 결과가 돌려준 행 키. 받은 값을 그대로 입력해 그 행을 고릅니다."
    • changedInput schema / properties / row_text_contains / description
      Previous value: -"Select the row whose full text contains this string."New value: +"행 전체 글자에 이 값이 들어 있는 행을 고릅니다."
    • changedInput schema / properties / to_date / description
      Previous value: -"Search range end date (YYYYMMDD)."New value: +"조회 종료일 YYYYMMDD."
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

The annotations supply readOnlyHint=false, destructiveHint=false and openWorldHint=false, but the description adds real context beyond that: each call consumes one token, the call creates an XBOSS job and stores processing results, and therefore the lookup is explicitly not purely read-only despite the institution source being only queried. It also explains reusing request_idempotency_key only to recover a lost request and warns that a same-named institution-side key is a different field. This is consistent with, and explanatory of, the readOnlyHint=false annotation.

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 description leads with the prerequisite call, then the action and return shape, then cost and side effects, which is good front-loading. The idempotency guidance is spread over four sentences and slightly repetitive, and the closing sentence about institution data changes and confirmation procedures is generic filler. Overall it is tight enough to read once and act on.

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 10-parameter tool with no output schema, the description does the heavy lifting: prerequisite call, cost per call, side effects, idempotency lifecycle, and the shape of the returned data including raw institution codes. What is missing is failure behavior — not-found notices, authentication failure, or how row_key and row_index are resolved when both are provided.

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?

With schema coverage at 100%, the baseline is 3, but the description adds meaningful semantics: row_key is described as coming from a preceding exploration result, account_link_id is tied to the login call and to having multiple certificates for the same institution, and the idempotency key has explicit lifecycle rules. It also warns against confusing request_idempotency_key with the institution-side idempotency_key field. It does not clarify how row_key, row_index and the text-contains filters interact when several are supplied.

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 action (open one premium notice detail sheet) plus the two alternative lookup paths (a row key from the exploration result, or notice year-month plus document name) and the fields returned (year-month, round, insurance type, item rows). It also explains that item names arrive as raw institution codes, which sharpens what the caller will actually see. It does not explicitly separate this tool from sibling detail tools such as edi_electronic_notices__detail or select, so it falls 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 gives an explicit prerequisite — call nhis_edi__session__login first with the same account_link_id — and states that the row key comes from a preceding exploration result, so the agent knows the required call order. It also says anonymous/trial calls cannot use the idempotency field. It stops short of naming a case where a different detail tool should be used instead.

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