Skip to main content
Glama

가입증명 발급 대상자 조회

nps_edi__b1__certificates__membership__subscribers__search

먼저 호출할 도구: nps_edi__auth__npki_session__login (같은 account_link_id). 국민연금 가입증명서(EC02)를 발급할 수 있는 사업장 가입자를 성명으로 조회합니다. 발급 도구에 넣을 row_index 와 row_key 를 가입자마다 돌려주며 주민등록번호는 돌려주지 않습니다. 로그인한 호출이면 첫 요청 전에 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": "nps_edi__b1__certificates__membership__subscribers__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_noNo쪽 번호. 기본 1.
search_textNo검색할 가입자 성명(srchData). 입력하지 않으면 전체 목록입니다.
page_per_countNo한 쪽에 받을 건수. 기본 10.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
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. Changed3 schema fields changed
    • changedInput schema / properties / page_no / description
      Previous value: -"Page number (default: 1)"New value: +"쪽 번호. 기본 1."
    • changedInput schema / properties / page_per_count / description
      Previous value: -"Items per page (default: 10)"New value: +"한 쪽에 받을 건수. 기본 10."
    • changedInput schema / properties / search_text / description
      Previous value: -"Subscriber name to search (srchData). Omit for the whole list."New value: +"검색할 가입자 성명(srchData). 입력하지 않으면 전체 목록입니다."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, and the description reinforces this by stating the call is not purely read-only because it creates an XBOSS job and stores the result, plus consumes one token per call. It also discloses a privacy behavior (resident registration numbers are never returned) and the idempotency retry semantics, which annotations cannot express.

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 prerequisite is front-loaded in the first clause, and each subsequent sentence covers a distinct concern (return values, idempotency, token cost, read-only caveat). It is longer than ideal and the idempotency explanation spans several sentences that could be tightened, but no sentence is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description compensates by stating exactly what is returned (row_index and row_key per subscriber) and what is deliberately withheld (resident registration number). Combined with the prerequisite, cost, and idempotency notes, an agent has everything needed to call this correctly.

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 adds real meaning: it explains how request_idempotency_key must be generated and reused, clarifies that account_link_id must match the login session, and separates the tool's idempotency field from the institution's own idempotency_key field. It does not elaborate on page_no/search_text beyond the schema, so it falls short of a 5.

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

Purpose5/5

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

The description names a specific verb and resource (look up workplace subscribers by name who are eligible for the EC02 membership certificate) and explicitly distinguishes this tool from the issuance tool by saying it returns row_index and row_key for that tool to consume. An agent can tell it apart from the sibling issue/apply tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the prerequisite explicitly ('먼저 호출할 도구: nps_edi__auth__npki_session__login (같은 account_link_id)'), explains the downstream handoff to the issuance tool, and gives when/when-not rules for the idempotency key (reuse only to recover an unanswered request, new value for a new execution, unavailable in account-less trial mode). It also warns not to confuse it with the institution-side idempotency_key field.

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