Skip to main content
Glama

국민연금 수급증명서 재발급 결과

get_nps_pension_payment_cert
Idempotent

req_nps_pension_payment_cert의 transactionId로 승인 상태와 국민연금 수급증명서 재발급 결과를 조회합니다. AUTH_WAITING이면 휴대폰 승인을 기다리고 COLLECTING이면 잠시 후 같은 ID로 조회하세요. 최초 결과 반환 시 과금되며 유효기간 내 재조회는 무료입니다. resultAvailable과 status, errorCode를 확인하세요. 결과는 result.npsPensionPaymentCert에 있으며 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_pension_payment_cert"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing billing behavior (60P on first result, free re-query within validity), the status state machine, and result expiration via resultExpiresAt. This context is consistent with readOnlyHint=false since a charge is incurred, so no contradiction. The description also tells the agent which fields (resultAvailable, status, errorCode) drive control flow.

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 and result location — a logical order with no wasted sentences. Slight redundancy in that billing is stated both in a sentence and again in the bracketed pricing note.

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?

With no output schema, the description still tells the agent where the payload lives (result.npsPensionPaymentCert), which fields to inspect, and how expiry is surfaced. That covers everything needed to call, poll, and interpret results for a single-parameter polling tool.

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% and the schema already documents the 32-char lowercase hex pattern required. The description adds the origin of the value (the response of req_nps_pension_payment_cert for the same product), which is meaning the schema alone does not convey.

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 (국민연금 수급증명서 재발급 결과) and explicitly ties it to the sibling request tool req_nps_pension_payment_cert as the source of the transactionId. An agent can immediately tell this is the polling/result counterpart rather than a new request.

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 guidance: AUTH_WAITING means wait for phone approval, COLLECTING means retry shortly with the same ID, and RESULT_EXPIRED means a fresh authentication request is required. It names the alternative tool to use for the initial request, so the when/when-not split is complete.

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.