Skip to main content
Glama

APICK Business

국민연금 연금산정용 가입내역 확인서 발급 결과

get_nps_career_cert
Idempotent

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

Input Schema

NameRequiredDescriptionDefault
transactionIdYes동일 상품의 req_nps_career_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 (60P charged on first result, free re-query within validity), the state machine (AUTH_WAITING, COLLECTING, RESULT_EXPIRED), and the fields to inspect (resultAvailable, status, errorCode). The annotations only say readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description supplies the cost and expiry behavior that matters for deciding when to call.

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 the purpose, then status handling, then billing, then result location and expiry. The pricing appears twice (inline and in the bracketed trailing note), which is slightly redundant but the rest is dense and earns its place.

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, so the description carries the return-value burden and does so: result payload path result.npsCareerCert, resultAvailable/status/errorCode, and resultExpiresAt. Combined with the polling states and billing rules, an agent has everything needed to call it correctly and interpret the response.

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 already documents the 32-character lowercase hex pattern, so the baseline is 3. The description adds provenance — that the ID must come from the matching req_nps_career_cert response — which helps an agent avoid mixing IDs across the many req_/get_ pairs.

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: polling the approval status and issuance result of a 국민연금 연금산정용 가입내역 확인서 using a transactionId from req_nps_career_cert. The pairing with the req_ sibling is made explicit, so an agent can tell the request step from the retrieve step without opening either 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?

Gives conditional routing: if AUTH_WAITING, wait for phone approval; if COLLECTING, poll again shortly with the same ID. It also names the prerequisite (transactionId from req_nps_career_cert) and the recovery action after resultExpiresAt (submit a new authentication request).

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.