Skip to main content
Glama

사업자등록증명 신청

hometax__certificate__apply__business_registration
Destructive

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 사업자등록증명(Certificate of Business Registration) 신청을 기관에 접수합니다. 되돌릴 수 없습니다. 접수하면 기관에 접수 기록(cvaId, rcatNo)이 남으며 취소 기능이 없습니다. 이 도구는 기관의 기록을 바꿉니다. 첫 호출은 실행되지 않고, 전송할 내용의 미리보기와 1회용 confirmation_token 을 돌려줍니다(오류 WRITE_CONFIRMATION_REQUIRED). 그 미리보기를 사용자에게 그대로 보여 줍니다. 사용자가 동의한 뒤에만 같은 인자에 그 confirmation_token 을 더해 다시 호출합니다. 사용자의 동의 없이 토큰을 넣지 않습니다. 인자를 하나라도 바꾸면 토큰은 무효가 됩니다. 그때는 토큰 없이 호출해 새 미리보기를 받습니다. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hometax__certificate__apply__business_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
adrOpYnNo주소 표시 여부(Y/N) (서식의 선택 입력)
amtOpYnNo금액 표시 여부(Y/N, 그 항목이 있는 서식에서만 반영) (서식의 선택 입력)
resnoOpYnNo주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)
cerpIsnRqsQtyNo발급 매수 (서식의 선택 입력)
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
cvaDcumGranMthdCdNo교부방법 코드 (서식의 선택 입력)
confirmation_tokenNo첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.
cvaDcumSbmsOrgnClCdNo제출처 구분코드 (서식의 선택 입력)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes far beyond the supplied destructiveHint=true/readOnlyHint=false annotations: it names the durable side effects (agency record with cvaId, rcatNo), states there is no cancellation, explains the two-phase confirmation flow and the WRITE_CONFIRMATION_REQUIRED error, and notes that a XBOSS job is created and results stored. It even warns that argument changes invalidate the token, which is exactly the kind of failure mode an agent needs to avoid.

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 the prerequisite and the core action, then the destructive warning, then the confirmation workflow — a sensible order. It is dense but every procedural sentence is load-bearing; the only soft spots are the moderately repetitive '이 도구는 기관의 기록을 바꿉니다' restatement and the trailing boilerplate about XBOSS jobs and per-tool confirmation procedures.

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 an irreversible, open-world write with no output schema, the description covers the prerequisite session, the confirmation handshake, the token lifecycle risk, the irreversibility, and the identifiers (cvaId, rcatNo) that come back. An agent has everything needed to call it safely; token expiry (10 minutes) is the one detail left to the schema, where it is already present.

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%, so all eight parameters are already documented, which sets the baseline at 3. The description adds only one genuinely new semantic constraint: confirmation_token must be paired with identical arguments and is invalidated by any change; the remaining parameters (adrOpYn, cerpIsnRqsQty, cvaDcumGranMthdCd, etc.) receive no extra meaning in the description text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource pair ('사업자등록증명 ... 신청을 기관에 접수합니다') with the target of the submission named. It is clearly distinguishable from the download/list siblings by the word '접수', but it never explicitly names the near alternatives such as business_registration_certificate_reissue or gov24__business_registration_certificate__issue, so the differentiation is implicit.

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 prerequisite (call hometax__session__login first with the same account_link_id) and a precise usage procedure: first call yields a preview plus confirmation_token, show the preview to the user, re-call with the token only after consent, and never insert the token without consent. It also prescribes the fallback when arguments change (call again without the token to get a fresh preview), leaving nothing 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.

Resources