Skip to main content
Glama

국세완납증명 신청

hometax__certificate__apply__national_tax_payment
Destructive

먼저 호출할 도구: hometax__session__login (같은 account_link_id). 국세완납증명(Tax Clearance Certificate) 신청을 기관에 접수합니다. 되돌릴 수 없습니다. 접수하면 기관에 접수 기록(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__national_tax_payment"
  }
}

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

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses that the action is irreversible, leaves institution-side records (cvaId, rcatNo) with no cancel function, mutates the institution's data, and spawns an XBOSS job whose result is stored. It also documents the two-phase write-confirmation protocol (WRITE_CONFIRMATION_REQUIRED, one-time token, invalidated by argument changes), which annotations alone 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is front-loaded and the confirmation protocol is laid out in sequence, so an agent can act on it directly. A few trailing sentences ('호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고...', '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다') read as boilerplate and partially repeat the irreversibility point.

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 an eight-parameter destructive submission tool with no output schema, the description covers prerequisites, consent gating, irreversibility, and side effects well. It could go slightly further by saying what the preview contains or where the issuing code (cvaDcumGranMthdCd, no enum) values come from.

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 meaning for confirmation_token: that it comes from the first call, must be echoed with identical arguments, must never be sent without user consent, and is invalidated if any argument changes. The eight form-code parameters are only explained by the schema, which is acceptable at full coverage.

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 names a specific verb and resource ('국세완납증명(Tax Clearance Certificate) 신청을 기관에 접수합니다') in both Korean and English gloss, and it states up front the prerequisite tool (hometax__session__login with the same account_link_id). An agent can tell this submission tool apart from the certificate-template/auto-apply siblings 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 Guidelines4/5

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

It gives clear preconditions (call login first, same account_link_id) and explicit when-not rules: never include the confirmation_token without user consent, and if any argument changes, call again without the token to obtain a fresh preview. What is missing is differentiation from the other certificate application siblings (apply_auto, apply_with_template), but the confirmation flow itself is fully prescribed.

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