Skip to main content
Glama

국민연금 일시금 지급내역 발급 인증 요청

req_nps_lump_sum_cert

국민연금 일시금 지급내역 발급을 위한 본인 간편인증을 요청합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_nps_lump_sum_cert에 transactionId를 전달하세요. 승인 대기 중 인증 요청을 반복하거나 자동 승인하지 마세요. [인증 발송 성공 시 20P]

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": {
      "name": "<name>",
      "birthDate": "<birthDate>",
      "phone": "<phone>",
      "authProvider": "<authProvider>"
    },
    "name": "req_nps_lump_sum_cert"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdfNotrue 이면 증명서 PDF를 함께 발급 (생략 시 조회값만)
langNo발급 언어 (K 국문·E 영문, 생략 시 K)
nameYes본인 이름
phoneYes본인 명의 휴대전화 번호 (숫자만)
telcoNo통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰
formatNo응답 형식 (json=조회값만·pdf=PDF base64만·both=둘 다, 생략 시 json). 대화형 사용은 응답이 작은 json 을 권장
purposeNo발급 용도 (01 개인 확인용·02 공공기관 제출용·03 금융기관 제출용·04 기타, 생략 시 01)
birthDateYes생년월일 8자리 (YYYYMMDD)
authProviderYes휴대폰에서 승인할 간편인증 방식

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so this matches the described side-effecting, non-idempotent request flow with no contradiction — in fact the explicit 'do not repeat while pending' warning reinforces the non-idempotent annotation. However the description does not disclose what the authentication request actually persists, what happens to a pending transaction that is never approved (expiry, orphaned state), or how long the pending window lasts. Those operational facts matter for a non-idempotent, billed external call yet are absent.

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?

Purpose is front-loaded and each sentence contributes a distinct operational fact: cost side-effect, return values, next step, and a prohibition. The only minor waste is that the billing point is stated twice ('접수 과금이 발생' and '[인증 발송 성공 시 20P]'), and the whole thing is one undivided paragraph despite containing four separable rules.

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?

For an asynchronous two-step authentication flow with no output schema, the description covers everything an agent needs: it names the returned fields, explains the hand-off to get_nps_lump_sum_cert, warns about the real-world phone notification, and flags the point charge. The pending-approval loop behavior is also constrained.

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 description coverage is 100%, so the schema already carries the full meaning of all 9 parameters, including enum values and the telco/authProvider dependency. The description adds no parameter-level detail beyond what the schema states — the transactionId and status it mentions are outputs, not inputs. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence names a specific verb (요청) and resource (국민연금 일시금 지급내역 발급을 위한 본인 간편인증), making clear this initiates an authentication flow rather than retrieving a certificate. It is directly distinguishable from the sibling get_nps_lump_sum_cert, which the description itself names as the follow-up step.

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?

Explicit pre-call guidance is given ('사용자 확인 후 호출하세요'), explicit prohibitions are stated ('승인 대기 중 인증 요청을 반복하거나 자동 승인하지 마세요'), and the correct sequencing alternative is named ('승인 후 get_nps_lump_sum_cert에 transactionId를 전달하세요'). Nothing about when to use this versus the retrieval sibling is left to inference.

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.