Skip to main content
Glama

APICK Business

국민연금 연금소득 원천징수영수증 발급 결과

get_nps_pension_tax_cert
Idempotent

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The description adds substantial context beyond the annotations: per-call billing of 60P on first result, free re-queries while waiting or within the validity window, the resultExpiresAt boundary, and the status/errorCode fields to inspect. The only weakness is that it does not clarify why readOnlyHint is false, though the billing note effectively implies a chargeable operation.

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?

Core polling logic and state handling are front-loaded in the first two sentences, which is good structure. However, the trailing bracketed price note duplicates the earlier sentence about 60P first-result charging and free re-queries.

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 compensates by naming the result path (result.npsPensionTaxCert), the gating fields (resultAvailable, status, errorCode), and the expiry/error behavior. An agent has everything needed to poll correctly and handle terminal states.

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?

Schema coverage is 100% and the schema already specifies the 32-character lowercase hex pattern and the origin of the value. The description only restates that the ID comes from the same product's request response, adding little beyond the schema baseline.

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 it explicitly to the sibling req_nps_pension_tax_cert whose transactionId it consumes. An agent can immediately distinguish this polling tool from the request-side sibling.

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 gives concrete conditional routing: AUTH_WAITING means wait for phone approval, COLLECTING means re-poll shortly with the same ID, and RESULT_EXPIRED means a new authorization request is required. The prerequisite (transactionId from req_nps_pension_tax_cert) is stated up front.

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.