Skip to main content
Glama

홈택스 원천세 정기신고 초안 초기화

hometax__tax__withholding__regular_report__init
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Initialize a Hometax regular-withholding draft. This writes to the institution. The first call is not executed: it returns a preview of exactly what will be sent and a one-time confirmation_token (error WRITE_CONFIRMATION_REQUIRED). Show that preview to the user as it is. Only after the user agrees, call again with the same arguments plus that confirmation_token. Never add the token without the user's agreement. Changing any argument makes the token invalid; call without the token to get a new preview. Exception: with draft_mode=resume the call only reads the return already in progress (nothing is written or deleted at the institution), so it runs at once and returns no confirmation_token. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": {
      "periods": "<periods>"
    },
    "name": "hometax__tax__withholding__regular_report__init"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodsYessubmitYm, attrYm, pymnYm period object
draft_modeNo작성 방식. new(기본값)는 새 신고서로 작성하며, 이미 작성 중인 신고서가 있으면 그것을 지우고 시작합니다. resume 은 작성 중인 신고서를 이어서 씁니다. init 과 basic_save 에 같은 값을 입력해 주세요.
fixture_keyNoOptional local fixture key
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
confirmation_tokenNo첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

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?

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds far more: the two-phase confirmation gate, the WRITE_CONFIRMATION_REQUIRED error code, one-time token semantics, token invalidation on argument change, and XBOSS job creation with per-call token consumption. It also explicitly carves out the draft_mode=resume case as read-only, which explains why the annotation profile appears write-oriented.

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, then the execution flow, then the resume-mode exception, which is the right priority order. The trailing Korean block partially restates earlier points about confirmation and read-only status, but it still carries the XBOSS job-creation disclosure; the description is long yet nearly all load-bearing.

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 destructive multi-step mutation with no output schema, the description supplies everything an agent needs: prerequisite auth, first-call return shape (preview plus token), error signal, resubmission rule, and the mode-specific exception. Nothing material is left to inference.

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?

With 100% schema description coverage, the baseline is 3. The description adds genuine meaning beyond the schema: it ties account_link_id to the login session, explains the confirmation_token lifecycle (one-time use, invalidated by any argument change, refresh by omitting it), and clarifies that resume mode short-circuits the confirmation flow. The nested periods object is left to the schema, which is acceptable.

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: 'Initialize a Hometax regular-withholding draft', and the title reinforces it as draft initialization. It does not explicitly contrast itself with the sibling inits for amendment or late reports, but the qualifier 'regular-withholding' plus the naming convention already narrows it well enough that an agent can pick it out.

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?

Opens with a hard prerequisite ('REQUIRES prior hometax__session__login call with same account_link_id') and then defines the exact two-call protocol: first call returns a preview, second call with the token executes. It also names what not to do ('Never add the token without the user's agreement') and gives the recovery path ('call without the token to get a new preview') when arguments change.

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