Skip to main content
Glama

APICK Business

국민연금 가입자증명서 발급 인증 요청

req_nps_member_cert

국민연금 가입자증명서 발급을 위한 본인 간편인증을 요청합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_nps_member_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_member_cert"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdfNotrue 이면 증명서 PDF를 함께 발급 (생략 시 조회값만)
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 을 권장
maskRrnNo증명서의 주민등록번호 뒤 6자리 가림 (생략 시 true)
purposeNo발급 용도 (01 개인 확인용·02 공공기관 제출용·03 금융기관 제출용·04 기타, 생략 시 01)
birthDateYes생년월일 8자리 (YYYYMMDD)
authProviderYes휴대폰에서 승인할 간편인증 방식

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, a thin profile. The description goes well beyond: it discloses the out-of-band push notification to the user's phone, a per-request charge, the non-idempotent two-phase approval flow, the transactionId/status return contract, and a 20P reward on successful dispatch — all behavior an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences in a deliberate order: purpose, cost warning, return/next-step contract, prohibition. Front-loaded and free of filler; the bracketed reward note is the only optional element and it is placed last.

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?

No output schema exists, but the description still specifies what comes back (transactionId and status) and what to do with it, which is exactly the missing piece for a two-phase async tool. With 9 parameters at full schema coverage and a destructive=false/openWorld profile, nothing needed to call it correctly is absent.

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% and four parameters carry enums, so the schema already documents name, birthDate, phone, authProvider, telco, format, maskRrn and purpose in detail. The description adds no parameter-level meaning at all — notably the telco-required-when-authProvider=pass dependency and the pdf/format interaction live only in the schema — so the baseline 3 applies.

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?

Names a specific verb and resource (requesting simple identity authentication for NPS 가입자증명서 issuance) and explicitly positions itself as the first half of a two-step flow whose second half is get_nps_member_cert. An agent can separate it from the get_* siblings 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?

States the trigger (issuing a member certificate), the required pre-condition (confirm with the user because a push and a billing charge occur), the mandatory next step (pass transactionId to get_nps_member_cert after approval), and two explicit prohibitions (no repeat requests while pending, no auto-approval). Both when-to-use and when-not-to-use are covered.

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.