Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

홈택스 원천세 수정신고 작성 취소

hometax__tax__withholding__amendment_report__cancel_draft
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. 기관에 작성 중인 원천세 수정신고서를 취소합니다. 취소하면 그 작성 중 신고서를 되살릴 수 없습니다. 이미 접수된 신고는 취소하지 않으며 접수된 신고를 지우려면 신고 삭제신청을 쓰세요. 그 작성 중 신고서를 다룬 직전 단계의 job_id 를 source_job_id 로 넘깁니다. 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. 호출마다 토큰 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": {
      "source_job_id": "<source_job_id>",
      "expected_snapshot_hash": "<expected_snapshot_hash>"
    },
    "name": "hometax__tax__withholding__amendment_report__cancel_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_job_idYes이어서 진행할 이전 단계 작업의 job_id 를 그대로 입력합니다(job_ 으로 시작하는 작업 번호). 작성 준비(init)부터 미리보기(preview)까지 작성 중인 상태의 결과, 또는 그 상태에서 실행한 조회(lookup) 결과를 받습니다. 제출(submit)이 끝난 신고서는 작성 취소할 수 없어 409 로 거절합니다. 같은 조직과 환경, 같은 기관 연결에서 이 신고 유형으로 성공한 작업이어야 하고 아니면 진행하지 않고 거절하며, 받지 않는 작성 상태의 결과이면 409 로 거절합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
confirmation_tokenNo첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.
expected_snapshot_hashYessource_job_id 작업 결과의 snapshot_hash 를 그대로 입력합니다(소문자 16진수 64자리). 그 작업의 내용과 맞지 않으면 진행하지 않고 작성 내용이 바뀌었다는 오류(409)로 거절합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, readOnlyHint=false) by stating the change is irreversible ('되살릴 수 없습니다'), that submitted filings are rejected, that a preview must be shown to the user verbatim, and that each call creates an XBOSS job and consumes a quota token. It explicitly warns the agent not to add the confirmation_token without user agreement, which is real operational guidance.

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-loads the login prerequisite and the cancellation effect, then the confirmation protocol, which is the right order. It is longer than needed: the closing sentences about creating an XBOSS job, 'this writes to the institution', and 'this call is not purely read-only' restate the same point three times and could be consolidated into one line.

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?

With no output schema, the description still tells the agent what comes back (a preview plus a one-time confirmation_token surfaced as WRITE_CONFIRMATION_REQUIRED) and how to complete the write. Prerequisite session state, rejection conditions, and irreversibility are all covered for a destructive, open-world-false mutation.

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 the schema already explains all four parameters including token expiry and snapshot hash matching. The description adds only a small amount of framing: that source_job_id should be the immediately preceding step (init through preview or lookup) and that submitted reports return 409. That is marginal value over the already-documented schema, so baseline 3 applies.

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?

States a specific verb and resource: cancels an in-progress withholding amendment report draft at the institution ('기관에 작성 중인 원천세 수정신고서를 취소합니다'). It also bounds the scope by excluding already-submitted filings, so an agent can distinguish this from a receipt-deletion operation without opening the schema.

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 (prior hometax__session__login with the same account_link_id), an explicit when-not (already-submitted reports cannot be cancelled; use the filing deletion request instead), and a precise two-call protocol: first call returns a preview and token, second call with the same arguments plus token executes. The condition that changed arguments invalidate the token is also spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources