Skip to main content
Glama

국민연금 개인회생 신청용 확인서 발급 인증 요청

req_nps_rehabilitation_cert

국민연금 개인회생 신청용 확인서 발급을 위한 본인 간편인증을 요청합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_nps_rehabilitation_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_rehabilitation_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.6/5.0
Behavior5/5

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

The annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), but the description adds concrete behavior the agent cannot infer from them: a push notification goes out, a 20P charge is incurred per successful send, the call is a two-phase handshake that returns transactionId and status, and repeating the request while approval is pending must be avoided. That last point substantively explains the non-idempotent nature declared in the annotations.

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?

The structure is well front-loaded: the purpose comes first, then the cost warning, then the return-value and handoff mechanics, then the prohibitions. The one inefficiency is that billing is stated twice (once in the sentence about notifications and reception billing, once in the bracketed [20P] note).

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?

There is no output schema, and the description fills that gap by naming the returned values (transactionId, status) and explaining how they are consumed. For an eight-parameter, non-idempotent, open-world authentication request, it covers cost, sequencing, and the failure mode of duplicate sends.

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 all eight params, including the four enums and the telco/authProvider constraint, are documented in the schema itself. The description mentions no parameter names or formats, so it adds no meaning beyond what the schema already provides; the baseline of 3 is 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?

The description names a concrete action (requesting simple self-authentication) tied to a specific document (the NPS personal-rehabilitation application confirmation), so it is not merely a restatement of a vague name. It also distinguishes itself from sibling get_nps_rehabilitation_cert by explaining that the tool's output (transactionId) feeds into that tool.

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 explicit conditions for when to call (only after user confirmation), what to do next (guide the user to approve on their phone, then pass transactionId to get_nps_rehabilitation_cert), and what not to do (do not re-send while approval is pending, do not auto-approve). The handoff to the sibling tool is spelled out, so almost nothing is left to the agent to infer.

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.