Skip to main content
Glama

개인 국세 통합조회 인증 요청

req_hometax_bundle

개인 국세 통합조회를 위한 본인 간편인증을 요청합니다. products 로 조회할 상품을 고르면 고른 상품만 승인 한 번으로 실행하고, 단가는 고른 상품 단가의 합입니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_hometax_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>",
      "products": "<products>"
    },
    "name": "req_hometax_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes본인 이름
yearNo증명 귀속연도 4자리 (증명을 고를 때 사용)
phoneYes본인 명의 휴대전화 번호 (숫자만)
telcoNo통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰
yearsNo신고·납부내역 조회 연수 (1~10, 생략 시 1)
formatNo증명 응답 형식 (생략 시 both)
engl_ynNo영문 증명 여부 (Y/N, 생략 시 N)
itrf_cdNo증명 발급 사유 코드 (서버 공통코드)
deliveryNo교부방법 (06 프린터·10 화면·04 팩스·12 전자문서지갑)
issuanceNo증명 발급 구분 (서버 공통코드)
productsYes조회할 상품 키 (1개 이상). personal_income·cash_receipt_deduction·income_by_payer·income_data_check·tax_return_history·tax_payment_history·income_amount_cert·pension_credit_cert·fact_cert
quantityNo발급 희망 수량 (1~5, 생략 시 1)
birthDateYes생년월일 8자리 (YYYYMMDD)
end_monthNo증명 조회 종료 월 (01~12)
submit_toNo제출처 코드 2자리 (증명을 고를 때 사용)
incomeYearsNo소득·현금영수증 조회 연수 (1~5, 생략 시 1)
start_monthNo증명 조회 시작 월 (01~12)
use_purposeNo사용용도 코드 2자리 (증명을 고를 때 사용)
authProviderYes휴대폰에서 승인할 간편인증 방식
resno_open_ynNo주민등록번호 공개 여부 (Y/N)
amount_open_ynNo소득금액증명 금액 공개 여부 (Y/N)
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.7/5.0
Behavior5/5

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

The annotations already indicate non-read-only, non-idempotent, and open-world behavior. The description adds substantial context beyond that: mobile notification dispatch and reception billing (접수 과금), returned transactionId and status, a 20P success credit, and an explicit no-repeat/no-auto-approve rule while approval is pending.

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?

The description is six sentences with purpose front-loaded, followed by products/pricing, cost warning, return/next step, caution, and credit. Every sentence carries operational meaning and there is no redundant wording.

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 24-parameter authentication tool with no output schema, the description covers the return fields, the required follow-up call, user-confirmation and billing concerns, and anti-repeat behavior. The schema documents every parameter, so nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning for the products parameter: selecting products executes only those products with one approval and the unit price is the sum of the selected product unit prices. This pricing and multi-select semantics is not conveyed by the schema's short product-key list.

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 states a specific verb (요청합니다) and resource (개인 국세 통합조회 본인 간편인증), and the personal scope distinguishes it from the business sibling req_hometax_biz_bundle. It also names get_hometax_bundle as the post-approval step, so the agent can identify the tool's role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to call after user confirmation, to pass transactionId to get_hometax_bundle after approval, and not to repeat requests or auto-approve while pending. It does not compare against other req_* alternatives such as income-certificate or business bundles, so exclusion guidance is limited.

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.