Skip to main content
Glama

국민연금 통합조회 인증 요청

req_nps_bundle

국민연금 통합조회를 위한 본인 간편인증을 요청합니다. 승인 한 번으로 담긴 증명 3종을 차례로 발급합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_nps_bundle에 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_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo가입내역·경력 조회 종료 월 (YYYY-MM, 선택)
fromNo가입내역·경력 조회 시작 월 (YYYY-MM, 선택)
nameYes본인 이름
phoneYes본인 명의 휴대전화 번호 (숫자만)
telcoNo통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰
yearsNo소득공제용 납부확인서 조회 연수 (1~5, 생략 시 1)
birthDateYes생년월일 8자리 (YYYYMMDD)
authProviderYes휴대폰에서 승인할 간편인증 방식

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / telco / description
      Previous value: -"통신사 코드 (authProvider=pass(통신사 PASS)일 때만 필수: S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰)"New value: +"통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰"
  2. Changed1 schema field changed
    • addedInput schema / properties / telco
      Added value: +{
      +  "description": "통신사 코드 (authProvider=pass(통신사 PASS)일 때만 필수: S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰)",
      +  "enum": [
      +    "S",
      +    "K",
      +    "L",
      +    "SA",
      +    "KA",
      +    "LA"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is not read-only, not idempotent, and open-world; the description adds the facts that matter: a push notification is sent to the user's phone, a per-request fee/point charge is incurred ("[인증 발송 성공 시 20P]"), and the call is asynchronous, returning transactionId and status rather than the documents. It also warns against retry storms during pending approval, which is exactly the behavioral risk of a non-idempotent outbound auth request.

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 purpose and the cost/confirmation warning are front-loaded, and the sequence of sentences reads as purpose → side effects → return values → next step. Slight redundancy in mentioning billing twice ("접수 과금이 발생" and the trailing "20P" note) keeps it from being maximally tight.

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, so the description carries the return contract itself (transactionId와 status) and the follow-up handoff to get_nps_bundle, plus the cost and anti-retry constraints. For an asynchronous, billed, non-idempotent auth-initiation tool, nothing an agent needs to call it safely is missing.

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 telco's conditional requirement and the from/to/years ranges is documented there, so the description needn't restate them. The description adds only implicit context (that the three certificates come as one bundle), which is below the level of parameter-level meaning, 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?

States a specific verb and resource ("국민연금 통합조회를 위한 본인 간편인증을 요청합니다") and clarifies the scope of the resulting bundle ("담긴 증명 3종을 차례로 발급"). It also names the companion tool get_nps_bundle as the next step, so an agent can distinguish this initiation call from the retrieval call and from the single-document req_nps_* siblings.

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 an explicit precondition ("휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요") and an explicit prohibition ("승인 대기 중 인증 요청을 반복하거나 자동 승인하지 마세요"). It also routes the agent forward ("승인 후 get_nps_bundle에 transactionId를 전달하세요"), which is a complete when/how-to-use story.

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.