Skip to main content
Glama

소득 증빙서류 통합발급 인증 요청

req_income_cert_bundle

소득 증빙서류 통합발급을 위한 본인 간편인증을 요청합니다. 승인 한 번으로 담긴 증명 2종을 차례로 발급합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_income_cert_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>",
      "year": "<year>",
      "use_purpose": "<use_purpose>",
      "submit_to": "<submit_to>",
      "delivery": "<delivery>"
    },
    "name": "req_income_cert_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes본인 이름
yearYes귀속연도 4자리 (최근 5년, 예: 2025)
emailNo수령 이메일 (선택, 생략 시 회원정보)
phoneYes본인 명의 휴대전화 번호 (숫자만)
telcoNo통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰
fax_noNo팩스번호 (delivery=04 일 때 필수)
formatNo응답 형식 (pdf=PDF base64만·json=PDF를 읽은 값만·both=둘 다, 생략 시 both). 대화형 사용은 응답이 작은 json 을 권장
deliveryYes교부방법 (06 프린터·10 화면·04 팩스·12 전자문서지갑). 문서는 응답으로 받으므로 보통 06
quantityNo발급 희망 수량 (1~5, 생략 시 1)
birthDateYes생년월일 8자리 (YYYYMMDD)
submit_toYes제출처 코드 2자리 (예: 99 기타)
use_purposeYes사용용도 코드 2자리 (예: 99 기타)
authProviderYes휴대폰에서 승인할 간편인증 방식
resno_open_ynNo주민등록번호 공개 여부 (Y/N)
amount_open_ynNo소득금액증명 금액 공개 여부 (Y/N)
wallet_addressNo전자문서지갑 주소 (delivery=12 일 때 필수)
address_open_ynNo주소 공개 여부 (Y/N)
income_source_open_ynNo소득금액증명 소득발생처 공개 여부 (Y/N)
withholding_all_print_ynNo소득금액증명 원천징수의무자 전체 표시 (Y/N)

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.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses real side effects: a push notification to the user's phone, a receiving charge, and a 20P cost on successful auth send — none of which is derivable from openWorldHint=false/true or destructiveHint=false. It also explains the two-phase flow and returns transactionId/status. It does not state timeouts or what happens if the user rejects, which keeps it short of a 5.

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?

Five short sentences, front-loaded with purpose and the cost warning, then the return values, then the sequencing constraint. Every sentence carries actionable information; nothing is restated from the schema.

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?

For a 19-parameter, non-idempotent, externally-visible authentication request with no output schema, the description supplies the missing pieces: the return fields (transactionId, status), the follow-up tool, the cost, and the prohibition on retrying. An agent has enough to invoke and sequence it correctly.

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 9 of 19 parameters are enums with inline explanations, so the schema already carries the parameter burden. The description adds no per-parameter guidance and only obliquely clarifies bundle composition ('담긴 증명 2종'). Baseline 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?

States a specific verb and resource ('소득 증빙서류 통합발급을 위한 본인 간편인증을 요청'), and clarifies a non-obvious detail: one approval issues two bundled certificates in sequence. It also names the companion tool get_income_cert_bundle, so an agent can separate the request step from the retrieval 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?

Explicitly gates the call on user confirmation, warns against repeating requests while approval is pending, forbids auto-approval, and names the exact follow-up ('승인 후 get_income_cert_bundle에 transactionId를 전달하세요'). Both when-to-use and when-not-to-use are covered, plus the correct next step.

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.