Skip to main content
Glama

국민연금 개인회생 신청용 확인서 발급 결과

get_nps_rehabilitation_cert
Idempotent

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: billing (60P on first result, free while waiting and within validity), status state machine (AUTH_WAITING, COLLECTING), expiry (RESULT_EXPIRED) and the errorCode/resultAvailable fields to check. It is consistent with readOnlyHint=false (billing side effect) and idempotentHint=true (free re-query). It stops short of saying what happens on other failure codes or whether the 60P is charged when the result never materializes.

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 progression through states, billing, and result location. Dense but every sentence carries operational information; the bracketed pricing note slightly repeats the earlier billing sentence.

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 supplies the return structure (resultAvailable, status, errorCode, result.npsRehabilitationCert, resultExpiresAt), the status values, expiry semantics, and cost model. That is everything an agent needs to poll and interpret results correctly.

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?

Only one parameter and schema coverage is 100%, so the schema already defines the transactionId format and origin. The description reinforces that it is the same ID from req_nps_rehabilitation_cert and must be reused across retries, which is useful but largely duplicative.

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 (국민연금 개인회생 신청용 확인서 발급 결과 + 승인 상태), keyed by the transactionId returned from req_nps_rehabilitation_cert. This clearly separates it from the sibling req_* tool that initiates the request.

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

Usage Guidelines4/5

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

Gives concrete polling guidance: AUTH_WAITING means waiting for phone approval, COLLECTING means retry shortly with the same ID, and after resultExpiresAt a new 인증 접수가 필요하다. It names the source tool but does not explicitly restate the prerequisite ordering (must call req_ first) or any other alternative beyond the retry loop.

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.