Skip to main content
Glama

APICK Business

국민연금 일시금 지급내역 발급 결과

get_nps_lump_sum_cert
Idempotent

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

Input Schema

NameRequiredDescriptionDefault
transactionIdYes동일 상품의 req_nps_lump_sum_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?

Annotations only say readOnlyHint=false and idempotentHint=true; the description explains why a lookup is not read-only by disclosing billing (first result 60P, free re-query within the validity window). It also documents the status codes, errorCode, result location, and expiry behavior — substantial context beyond the structured fields, with no contradiction of the annotations.

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 core action, then ordered by operational flow (approval states → billing → result inspection → expiry). Slightly redundant, since the pricing is stated once in prose and again in the bracketed note, but no sentence is wasted.

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 contract itself and does so: result.npsLumpSumCert, resultAvailable/status/errorCode, and resultExpiresAt. For a single-parameter polling tool this covers everything an agent needs 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 the pattern/format is already documented, so the baseline is 3. The description adds provenance the schema lacks: the transactionId must be taken from the req_nps_lump_sum_cert response for the same product, which prevents cross-product reuse errors.

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 (국민연금 일시금 지급내역 발급 결과) and ties itself explicitly to the req_nps_lump_sum_cert sibling that produces the transactionId. An agent can tell this is the polling/retrieval counterpart of the request tool 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 precondition (transactionId from req_nps_lump_sum_cert), the in-progress branches with explicit actions (AUTH_WAITING = mobile approval pending; COLLECTING = retry shortly with the same ID), and the terminal branch (after resultExpiresAt, RESULT_EXPIRED means a new auth request is required). When-to-use and when-to-restart are both fully specified.

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.