Skip to main content
Glama

국민연금보험료 납부확인서 발급 인증 요청

req_nps_paid_cert

국민연금보험료 납부확인서 발급을 위한 본인 간편인증을 요청합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_nps_paid_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_paid_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 을 권장
toYearNo조회 끝 연도 4자리 (생략 시 올해)
purposeNo발급 용도 (01 개인 확인용·02 공공기관 제출용·03 금융기관 제출용·04 기타, 생략 시 01)
fromYearNo조회 시작 연도 4자리 (생략 시 1988)
birthDateYes생년월일 8자리 (YYYYMMDD)
workplaceNoNo사업장관리번호 (생략 시 가장 최근 사업장)
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 give the generic openWorldHint/readOnlyHint=false profile; the description adds the concrete side effects an agent cannot infer: a mobile push notification is dispatched to the user's phone and a 20P charge is incurred on successful dispatch. It also discloses the return contract (transactionId plus status) and the anti-pattern of re-requesting while approval is pending, which is real behavioral context beyond the 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?

Purpose is front-loaded in the first clause, followed by the cost/billing warning, then the return-and-handoff flow, then the prohibition. Every sentence carries a distinct operational fact with no restatement of the name or title.

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?

Despite 11 parameters and no output schema, the description supplies the return shape (transactionId, status), the billing cost, the user-confirmation prerequisite, and the two-step flow into get_nps_paid_cert. Combined with a fully documented schema, an agent has everything needed to call this correctly and to avoid the costly misuse mode.

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 every parameter, including the telco enum and its 400-rejection behavior and the format guidance, is already documented in the schema. The description adds no parameter-level meaning beyond the returned transactionId, so 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?

The description names a specific verb and resource: it requests a simple mobile identity authentication (본인 간편인증) for issuing the National Pension premium payment certificate. It also names the sibling it hands off to (get_nps_paid_cert), so the agent can distinguish this prepare/authenticate step from the retrieve step 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?

It states the precondition for calling (after confirming with the user, since a push is sent and points are billed), the explicit prohibition (do not repeat the auth request while approval is pending, do not auto-approve), and the exact alternative/next step (pass transactionId to get_nps_paid_cert). 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.