Skip to main content
Glama

APICK Business

국민연금 가입자증명서 발급 결과

get_nps_member_cert
Idempotent

req_nps_member_cert의 transactionId로 승인 상태와 국민연금 가입자증명서 발급 결과를 조회합니다. AUTH_WAITING이면 휴대폰 승인을 기다리고 COLLECTING이면 잠시 후 같은 ID로 조회하세요. 최초 결과 반환 시 과금되며 유효기간 내 재조회는 무료입니다. resultAvailable과 status, errorCode를 확인하세요. 결과는 result.npsMemberCert에 있으며 resultExpiresAt 이후에는 RESULT_EXPIRED가 반환되어 새 인증 접수가 필요합니다. [최초 결과 60P (PDF 발급 포함 같은 금액); 대기·유효기간 내 재조회 무료]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transactionId": "<transactionId>"
    },
    "name": "get_nps_member_cert"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionIdYes동일 상품의 req_nps_member_cert 응답에서 받은 transactionId (소문자 16진수 32자리)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: it discloses a cost model (60P on first result return, including PDF issuance, with free polling and free re-reads inside the validity window) that the readOnlyHint=false flag alone does not convey, plus the status lifecycle and RESULT_EXPIRED behavior. What keeps it from a 5 is that retry cadence and what a failed/errorCode state means in terms of billing or re-issuance are left implicit.

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?

Front-loaded with purpose, then status handling, then billing, then result location and expiry — a sensible order with no filler sentences. The bracketed pricing note at the end largely repeats the '최초 결과 반환 시 과금 / 유효기간 내 재조회 무료' sentence, which is the only real redundancy.

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?

No output schema exists, so the description carries the return-shape burden and does so by naming result.npsMemberCert, resultAvailable, status, errorCode, and resultExpiresAt — enough for an agent to parse a response. It could be firmer about how long to wait between COLLECTING polls before giving up, which matters for an asynchronous tool.

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 coverage is 100% and the single transactionId is fully described in the schema, including the 32-char lowercase hex pattern, so the baseline is 3. The description restates the same provenance (from req_nps_member_cert) without adding new syntax or format meaning beyond the schema.

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?

States a specific verb and resource (조회 of approval status and 국민연금 가입자증명서 issuance result) and binds it to the exact input source: the transactionId returned by req_nps_member_cert. An agent can tell it apart from the sibling req_* tool that starts the workflow and from the other get_nps_*_cert readers by the certificate type.

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?

Gives explicit state-driven instructions rather than vague context: on AUTH_WAITING wait for phone approval, on COLLECTING poll again with the same ID shortly, and after resultExpiresAt expect RESULT_EXPIRED and a new 인증 접수. It also makes the pairing with req_nps_member_cert unambiguous, so the agent knows this is the second step of a two-call workflow.

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.