Skip to main content
Glama

APICK Business

사업자 증빙서류 통합발급 인증 요청

req_business_cert_bundle

사업자 증빙서류 통합발급을 위한 본인 간편인증을 요청합니다. 승인 한 번으로 담긴 증명 3종을 차례로 발급합니다. 휴대폰 알림 발송과 접수 과금이 발생하므로 사용자 확인 후 호출하세요. transactionId와 status를 반환하면 휴대폰 승인을 안내하고, 승인 후 get_business_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>",
      "business_no": "<business_no>",
      "year": "<year>",
      "use_purpose": "<use_purpose>",
      "submit_to": "<submit_to>",
      "delivery": "<delivery>"
    },
    "name": "req_business_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+알뜰폰
agreedNo대표자 본인 확인 동의. bind_id 가 없으면 true 여야 접수되며, 빠지면 인증을 보내지 않고 무과금으로 거절
fax_noNo팩스번호 (delivery=04 일 때 필수)
formatNo응답 형식 (pdf=PDF base64만·json=PDF를 읽은 값만·both=둘 다, 생략 시 both). 대화형 사용은 응답이 작은 json 을 권장
periodNo부가가치세 과세표준증명 과세기간 (1=1기·2=2기·all=연간)
bind_idNo이전 사업자 조회 결과의 bind_id (같은 계정·같은 사업자등록번호, 90일 이내면 agreed 없이 접수)
engl_ynNo영문 증명 여부 (Y/N, 생략 시 N)
deliveryYes교부방법 (06 프린터·10 화면·04 팩스·12 전자문서지갑). 문서는 응답으로 받으므로 보통 06
quantityNo발급 희망 수량 (1~5, 생략 시 1)
birthDateYes생년월일 8자리 (YYYYMMDD)
submit_toYes제출처 코드 2자리 (예: 99 기타)
business_noYes사업자등록번호 10자리 (숫자만)
use_purposeYes사용용도 코드 2자리 (예: 99 기타)
authProviderYes휴대폰에서 승인할 간편인증 방식
wallet_addressNo전자문서지갑 주소 (delivery=12 일 때 필수)

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

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

Annotations only declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds the concrete real-world behavior the agent actually needs: a mobile push is sent, a 20P charge is incurred on successful dispatch, the flow is two-phase and requires human approval on the phone, and retrying during the pending window is prohibited. That is substantive context beyond the annotations and directly prevents costly misuse.

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?

Front-loaded with purpose, then side effects, then the hand-off flow, then a prohibition; each sentence carries operational content. The trailing '[인증 발송 성공 시 20P]' partly restates the earlier billing warning, a minor redundancy in an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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, billable request tool with no output schema, the description supplies the critical missing pieces: what is returned (transactionId, status) and what the caller must do next. It does not describe what a rejection or 400 path looks like beyond the schema notes, but nothing essential for a correct first call is absent.

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% (19 params, conditional requirements for telco, fax_no, wallet_address, bind_id already documented inline), so the schema carries the parameter burden. The description adds no field-level meaning of its own; transactionId and status it mentions are return values, not inputs.

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?

Names a specific verb and resource (본인 간편인증 요청 for 사업자 증빙서류 통합발급) and states the outcome scope: one approval issues three certificate types in sequence. It also names the follow-up sibling get_business_cert_bundle, so the agent can distinguish this request step from the retrieval step without opening a 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?

Explicitly says to call only after user confirmation, to warn about the push notification and the 20P billing, not to repeat the request while approval is pending, and to hand transactionId to get_business_cert_bundle afterwards. It stops short of distinguishing this tool from the other request-style siblings (req_hometax_biz_bundle, req_income_cert_bundle), leaving the choice between document bundles to inference.

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.