Skip to main content
Glama

국민연금보험료 미납증명 발급 인증 요청

req_nps_contribution_unpaid_cert

국민연금보험료 미납증명 발급을 위한 본인 간편인증을 요청합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_nps_contribution_unpaid_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_contribution_unpaid_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 을 권장
purposeNo발급 용도 (01 개인 확인용·02 공공기관 제출용·03 금융기관 제출용·04 기타, 생략 시 01)
birthDateYes생년월일 8자리 (YYYYMMDD)
authProviderYes휴대폰에서 승인할 간편인증 방식

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?

Annotations already mark this as a non-read-only, non-idempotent, open-world call, but the description adds concrete consequences: a push notification is sent, the call incurs billing (20P on successful send), and the response is transactionId plus status. It stops short of describing failure modes or timeout/expiry behavior for the pending approval, which is the one gap.

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 sentences with no waste: purpose first, cost/warning second, next-step handoff third, prohibition fourth. Every sentence changes agent behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation-like auth tool with no output schema, the description covers the return values (transactionId, status), the follow-up call, and the cost. It does not cover how long a pending transaction stays valid or what a failed/expired approval looks like, which matters for an asynchronous phone-approval flow.

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 every parameter carries its own enum values and constraints (telco required for pass, 400 rejection, phone pattern), so the schema does the heavy lifting. The description adds no parameter-level detail beyond the returned transactionId, making the baseline 3 appropriate.

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 (국민연금보험료 미납증명 발급), and explicitly positions itself as the pre-step to get_nps_contribution_unpaid_cert. An agent can distinguish this request/authentication tool from the retrieval sibling without opening either 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 sequencing: call after user confirmation (SMS + billing), then after approval pass transactionId to get_nps_contribution_unpaid_cert. It also states when NOT to call again — no repeat requests while approval is pending and no auto-approval — which is exactly the failure mode for a verification tool.

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.