Skip to main content
Glama

증명서 신청 처리결과 검색

nps_edi__b1__certificates__application_results__search

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Search NPS certificate application and issuance results. 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__certificates__application_results__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNo쪽 번호. 기본 1.
end_dateNo조회 종료일 YYYYMMDD. 입력하지 않으면 오늘입니다.
start_dateNo조회 시작일 YYYYMMDD. 입력하지 않으면 오늘부터 90일 전입니다.
member_nameNo가입자 성명. 그 가입자의 건만 찾을 때 입력합니다.
template_codeNo서식 코드. 입력하지 않거나 A, ALL, 전체를 입력하면 모든 서식을 조회합니다.
page_per_countNo한 쪽에 받을 건수. 기본 10.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
row_text_containsNo결과 줄의 글자에 이 값이 들어 있는 줄만 고릅니다.
confirm_status_codeNo확인 상태 코드. 입력하지 않거나 A, ALL, 전체를 입력하면 모든 상태를 조회합니다.
processing_status_codeNo처리 상태. C 는 정상, S 는 오류입니다. 입력하지 않거나 A 를 입력하면 모든 상태를 조회합니다.
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?

The annotations show readOnlyHint=false and destructiveHint=false, and the description adds the important point that this call is not purely read-only: it creates an XBOSS job and stores processing results independent of whether the institution's source is queried, and it consumes one token per call. These details go well beyond the annotations. The residual gap is that it does not describe what the stored artifact or return payload looks like.

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 and idempotency guidance are properly front-loaded, but the text mixes English and Korean boilerplate and repeats the same idempotency guidance in both the description and the schema. Some of the trailing Korean sentences about XBOSS work and institutional data changes are dense and could be tightened.

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, zero-required search with full schema coverage and no output schema, the definition covers authentication prerequisites, token cost, the side-effect of creating an XBOSS job, and idempotency protocol. Only the shape of the returned results is left unaddressed, which is acceptable given the missing output schema.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains how request_idempotency_key must be generated, saved, reused only for lost-response recovery, and distinguished from a provider-specific key, and it clarifies the login prerequisite tied to account_link_id. That is meaningful added semantics beyond the schema.

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 definition states a specific verb and resource: it searches NPS certificate application and issuance results, matching the title's meaning. The scope is clear enough to distinguish it from document_view and from the declarations processing_results search, though the definition never explicitly names those alternatives.

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 requiring a prior nps_edi__auth__npki_session__login call with the same account_link_id, plus protocol for when to reuse versus mint a new request_idempotency_key. It does not explicitly state when to choose this tool over sibling search tools, so it does not reach the top of the scale.

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