Skip to main content
Glama

연금통지서 목록 조회

nps_edi__b1__pension_notification_documents__search

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Search pension notification documents. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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": "nps_edi__b1__pension_notification_documents__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNoMember list page number (default 1).
end_dateNoSearch end date YYYYMMDD. Defaults to today when omitted.
start_dateNoSearch start date YYYYMMDD. Defaults to 90 days before today when omitted.
member_nameNoMember name for the detail member search.
template_codeNoTemplate (document form) code. Search treats A / ALL / 전체 as all documents; detail supports ED33 only (others return UNSUPPORTED_PENSION_NOTIFICATION_TEMPLATE).
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
page_per_countNoMember list rows per page (default 10).
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
read_status_codeNoRead status: 01=unread, 05=read, 10=all (read+unread), blank=all.
row_text_containsNoPartial row text match filter.
member_resident_noNoMember resident registration number for the detail member search.
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

B3.1/5.0
Behavior4/5

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

Annotations only provide the readOnly/destructive/openWorld triad, and the description adds substantial context beyond them: per-call token consumption, job creation and result storage, artifact download_url valid 15 minutes with 7-day file retention, and the explicit warning that this is not a pure read-only call — consistent with readOnlyHint=false. It also explains anonymous recovery_receipt semantics and that a receipt grants access to one result only. The remaining gap is that failure modes and pagination/result-shape behavior are not described.

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 single useful sentence (the login prerequisite and the search purpose) is buried at the front of a long, unfocused paragraph that mixes authentication, artifact retention, anonymous receipts, idempotency, token cost, and a Korean-language disclaimer. Much of the receipt/idempotency text reads as generic cross-tool boilerplate rather than tool-specific information, so the structure works against scanning.

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 12 all-optional parameters and no output schema, the description does cover artifacts, retention, prerequisites, and idempotency reasonably well. What it omits matters for correct invocation: which parameters select the list mode versus the detail mode, how paging interacts with the result, and what the response contains beyond artifacts[].

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 description coverage is 100%, so all 12 parameters are already documented in the schema; the baseline of 3 applies. The description duplicates the xlsx artifact and idempotency-key semantics without adding syntax or edge-case meaning, and it does not clarify the ambiguous split between list-style params (page_no, page_per_count) and detail-style params (member_name, member_resident_no).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search pension notification documents" gives a clear verb+resource, but the definition is dominated by artifact/idempotency boilerplate and never distinguishes this from nps_edi__b1__pension_notification_documents__detail. The schema's own wording ("Member list page number" vs "detail member search" for member_name/member_resident_no) muddies whether this is a list or detail search, leaving the purpose only partially resolved.

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 a hard prerequisite (prior npki_session__login with the same account_link_id) and gives a concrete fallback path to xdata__job__result for expired artifact links, which is real usage guidance. However, there is no guidance on choosing this tool over pension_notices__search or the paired detail tool, and no statement of when this search should not be used.

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