Skip to main content
Glama

신고 처리 결과 조회 (국민연금)

nps_edi__b1__declarations__processing_results__search

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Search declaration processing results from NPS. 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__declarations__processing_results__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNo쪽 번호. 기본 1.
end_dateNo조회 종료일 YYYYMMDD. 입력하지 않으면 오늘입니다.
start_dateNo조회 시작일 YYYYMMDD. 입력하지 않으면 오늘부터 90일 전입니다.
document_noNo전자문서번호. 그 문서 한 건만 찾을 때 입력합니다.
status_codeNo처리 상태 코드. 입력하지 않거나 A, ALL, 전체를 입력하면 모든 상태를 조회합니다.
template_codeNo서식 코드. 입력하지 않거나 A, ALL, 전체를 입력하면 모든 서식을 조회합니다.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
page_per_countNo한 쪽에 받을 건수. 기본 5.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
row_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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description corroborates that with a useful disclosure that the call creates an XBOSS job and consumes one token per invocation, so it is not a pure read. It adds concrete retention behavior (download_url valid 15 minutes, files kept 7 days) and recovery semantics. Some of the boilerplate about anonymous recovery_receipt and pack_run_id reads as copied from an xdata job tool and may not apply here, which slightly dilutes the transparency.

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?

Front-loading the prerequisite is good, but the body is long and mixes generic cross-tool boilerplate (anonymous receipts, publishing, signing up) with this tool's actual behavior, and it switches languages mid-paragraph. Several sentences do not earn their place for a search operation.

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 an 11-parameter tool with no output schema, the description covers the important gaps: auth prerequisite, artifact/download lifetime, retention, recovery path, and idempotency rules. It is close to complete for correct invocation, with the main weakness being relevance of the anonymous-result narrative rather than missing operational facts.

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 genuinely extends meaning: it explains that account_link_id must match the login session, that output_formats places an xlsx under artifacts[], and how request_idempotency_key must be reused only to recover the same request and kept distinct from a provider idempotency_key. That is real semantic value beyond the schema text.

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: "Search declaration processing results from NPS". It is clear about the operation, but it never distinguishes this search from similarly named siblings such as nps_edi__b1__certificates__application_results__search or nhis_edi__hr_payroll__processing_results__list, leaving the agent to infer the difference from the name alone.

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 hard prerequisite ("REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id") and routes expired-link recovery explicitly to xdata__job__result with the job_id. What is missing is any statement about when to choose this search over the many sibling search tools in the catalog.

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