Skip to main content
Glama

사업자등록증 재발급 신청

hometax__certificate__apply__business_registration_reissue
Destructive

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 사업자등록증 재발급(Business Registration Certificate Reissuance) 신청을 기관에 접수합니다. 되돌릴 수 없습니다. 접수하면 기관에 접수 기록(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_reissue"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The description adds substantial context beyond the annotations: the action is irreversible, it leaves an agency record (cvaId, rcatNo) with no cancellation function, and each call creates an XBOSS job. Those points largely restate what destructiveHint=true and readOnlyHint=false already imply, though the specific 'no cancel / record persists' consequence is genuinely additive. It stops short of describing response payload shape or failure modes beyond the single WRITE_CONFIRMATION_REQUIRED path.

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?

Structure is good: the login prerequisite is front-loaded, followed by purpose, irreversibility, and the two-phase confirmation protocol. The final two sentences ('기관 원본의 조회 여부와 별개로...', '기관 데이터 변경은 도구별 실행 내용과...') are generic filler that restate the non-read-only nature already established earlier.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter destructive write tool with no output schema, the description covers the critical path: prerequisites, confirmation handshake, irreversibility, and what the first call returns. Gaps remain around the domain meaning of the form fields and what a successful submission returns beyond the cvaId/rcatNo mention, which matters for a filing tool.

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 lifecycle semantics for confirmation_token that the schema only partially covers: changing any argument invalidates the token and requires a token-free re-call to obtain a new preview. The remaining form fields (adrOpYn, resnoOpYn, cerpIsnRqsQty, cvaDcumGranMthdCd) get no extra explanation, leaving them to the schema.

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?

The description states a specific verb and resource: it files/receives a business registration certificate reissuance application with the agency ('사업자등록증 재발급 ... 신청을 기관에 접수합니다'). The 'reissuance' qualifier separates it conceptually from the initial-issuance sibling, but no sibling is named explicitly, so the differentiation is implicit rather than stated.

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?

Strong operational guidance: call hometax__session__login first with the same account_link_id, show the preview to the user verbatim, and only re-call with the confirmation_token after user consent. It also covers the recovery path when arguments change (re-call without the token for a fresh preview). It lacks any when-not or alternative-tool routing, which keeps it below a 5.

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