Skip to main content
Glama

국민연금보험료 미납증명 발급 결과

get_nps_contribution_unpaid_cert
Idempotent

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, and the description corroborates this by disclosing that the first result return incurs a charge (60P, PDF issuance included) while re-queries within the validity window are free — that billing side effect is exactly the kind of context annotations cannot carry. It also enumerates status values, errorCode, and the RESULT_EXPIRED failure mode. The only shortfall is that it does not say how long a COLLECTING retry should wait or how many attempts are reasonable.

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-path guidance — a sensible order for a polling tool. It is slightly over-long because the pricing rule is stated twice (once in prose, once in the bracketed footer), which is redundant rather than harmful.

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 it: resultAvailable, status, errorCode, the result.npsContributionUnpaidCert path, and resultExpiresAt are all named. Combined with the billing and expiry rules, an agent has everything needed to poll 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 parameter description already names the originating request tool and the 32-hex format, so the baseline would be 3. The description adds genuinely useful semantics: the same transactionId is reused for repeated polling, and it stays valid only until resultExpiresAt, which tells the agent the ID is a session handle rather than a one-shot key.

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: queries approval status and the issuance result of the NPS unpaid-contribution certificate using the transactionId returned by req_nps_contribution_unpaid_cert. The pairing with the request sibling is made explicit, so an agent can tell this polling tool apart from the many other get_nps_* result tools without opening a 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 explicit branch-by-branch guidance: on AUTH_WAITING the user is still approving on their phone, on COLLECTING re-query shortly with the same ID, and after resultExpiresAt a RESULT_EXPIRED response means a brand-new request is required. It also names the sibling that must be called first, so the when-to-use condition is 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.