Skip to main content
Glama

사업자 국세 통합조회 인증 요청

req_hometax_biz_bundle

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

Input Schema

NameRequiredDescriptionDefault
toNo전자세금계산서 조회 종료일 (YYYY-MM-DD)
fromNo전자세금계산서 조회 시작일 (YYYY-MM-DD)
nameYes본인 이름
yearNo증명·전자세금계산서 귀속연도 4자리
phoneYes본인 명의 휴대전화 번호 (숫자만)
telcoNo통신사 코드. authProvider=pass(통신사 PASS)일 때 필수이며, 빠지거나 허용값이 아니면 인증 요청 없이 400으로 거절합니다. S SKT·K KT·L LGU+·SA SKT알뜰폰·KA KT알뜰폰·LA LGU+알뜰폰
agreedNo대표자 본인 확인 동의. bind_id 가 없으면 true 여야 접수되며, 빠지면 인증을 보내지 않고 무과금으로 거절
formatNo증명 응답 형식 (생략 시 both)
periodNo부가가치세 과세기간 (1=1기·2=2기·all=연간)
bind_idNo이전 사업자 조회 결과의 bind_id (같은 계정·같은 사업자등록번호, 90일 이내면 agreed 없이 접수)
engl_ynNo영문 증명 여부 (Y/N, 생략 시 N)
itrf_cdNo증명 발급 사유 코드 (서버 공통코드)
keywordNo거래처·품목 검색어 (선택)
deliveryNo교부방법 (06 프린터·10 화면·04 팩스·12 전자문서지갑)
issuanceNo증명 발급 구분 (서버 공통코드)
productsYes조회할 상품 키 (1개 이상). business_sales·business_purchase·business_registration_cert·vat_tax_base_cert·financial_statement_cert·closure_cert·tax_clearance_cert·etax_sales_list·etax_purchase_list·etax_sales_summary·etax_purchase_summary·etax_stats·etax_client_list·etax_item_list·etax_status
quantityNo발급 희망 수량 (1~5, 생략 시 1)
birthDateYes생년월일 8자리 (YYYYMMDD)
cert_typeNo납세증명서 종류 (서버 공통코드)
end_monthNo조회 종료 월 (01~12)
submit_toNo제출처 코드 2자리
business_noYes사업자등록번호 10자리 (숫자만)
start_monthNo조회 시작 월 (01~12)
use_purposeNo사용용도 코드 2자리
authProviderYes휴대폰에서 승인할 간편인증 방식
businessYearNo사업자 매출·매입 조회 연도 4자리 (생략 시 최근)

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

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

Far exceeds the annotations: it discloses that a phone push alert is sent, that 접수 과금 and a 20P charge apply on success, what the call returns (transactionId, status), and that the call is non-idempotent in practice (do not retry while pending). This is exactly the payment/side-effect context the openWorldHint and idempotentHint=false annotations cannot convey.

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 sentences, front-loaded with the purpose, then products semantics, cost warning, return/handoff, and the prohibition. Every sentence introduces new, actionable information; nothing restates the schema or the 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?

For a 26-parameter, no-output-schema, non-idempotent auth-initiation tool, the description supplies the flow (request → user phone approval → get_hometax_biz_bundle), the cost, the return fields and the retry policy. Parameter-level detail is fully carried by the 100%-covered schema, so nothing critical 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 coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: products is a multi-select whose chosen keys run under a single approval and whose 단가 is summed, which tells the agent how product selection is billed. It does not add semantic hints for the other 25 parameters, so it stops short of a 5.

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 immediately distinguishes itself from the retrieval sibling by saying the result must be handed to get_hometax_biz_bundle. An agent can identify this as the initiation step of a two-call flow without opening any 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?

Gives an explicit precondition (사용자 확인 후 호출), an explicit prohibition (승인 대기 중 인증 요청 반복 금지, 자동 승인 금지), and an explicit handoff rule (승인 후 get_hometax_biz_bundle에 transactionId 전달). Both when-to-call and when-not-to-call are covered, with the alternative sibling named.

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.