Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

신고서 본문 수정신고 생성

hometax__tax__vat__amendment__create
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. 부가가치세 정기신고에서 신고서 본문 수정신고 생성 작업을 수행합니다. 호출마다 토큰 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": {
      "business_no": "<business_no>",
      "year": "<year>",
      "half": "<half>",
      "original_receipt_job_id": "<original_receipt_job_id>",
      "source_job_id": "<source_job_id>",
      "expected_snapshot_hash": "<expected_snapshot_hash>",
      "confirm_create_amendment": "<confirm_create_amendment>"
    },
    "name": "hometax__tax__vat__amendment__create"
  }
}

Input Schema

NameRequiredDescriptionDefault
halfYes과세 기수입니다. 1 은 1기(1월부터 6월), 2 는 2기(7월부터 12월)입니다. 당초 신고의 기간과 다르면 거절합니다.
yearYes수정할 당초 신고의 과세 연도입니다. 네 자리 정수로 입력합니다. 당초 신고의 기간과 다르면 거절합니다.
business_noYes수정신고서를 만들 사업자의 사업자등록번호입니다. 하이픈 없이 숫자 10자리로 입력합니다. 당초 신고의 사업자와 다르면 거절합니다.
period_kindNo신고 구분입니다. PRELIMINARY 는 예정신고(기수의 앞 석 달), FINAL 은 확정신고(기수 여섯 달)이고 입력하지 않으면 PRELIMINARY 입니다. 당초 신고와 같은 구분을 입력합니다.PRELIMINARY
source_job_idYesoriginal_receipt_job_id 와 같은 값을 입력합니다. 다르면 거절합니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
expected_snapshot_hashYes당초 접수 작업 결과의 snapshot_hash 를 그대로 입력합니다(16진수 64자리). 그 작업의 내용과 다르면 거절합니다.
original_receipt_job_idYes수정할 당초 신고의 접수 작업 job_id 입니다. 같은 기관 연결로 이 서비스에서 제출해 접수가 확인된 신고의 작업이어야 하고, 그런 작업이 없거나 사업자와 기간이 다르면 거절합니다.
confirm_create_amendmentYes기관에 수정신고서를 새로 만드는 데 대한 사용자의 확인입니다. 사용자에게 확인을 받은 뒤 JSON 불리언 true 로 입력합니다. true 가 아니면 만들지 않고 거절합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, and the description adds real context beyond them: a token is consumed per call, an XBOSS job is created and its result persisted, and the operation is explicitly not a pure read regardless of whether the agency original is queried. It stops short of saying whether an amendment can be revoked or what happens to the original filing record.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The prerequisite requirement is correctly front-loaded and the token/job cost sentences earn their place. The trailing sentences ('순수 읽기 전용이 아닙니다', '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다') are boilerplate that restate or hedge without adding actionable detail.

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 destructive, 9-parameter, token-costing create with no output schema, the definition covers the login prerequisite, cost, and job creation. It never indicates what the call returns (e.g., a job id or receipt reference) or what the per-tool confirmation procedure actually is, leaving a gap for an agent that must chain this into a follow-up step.

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 a cross-parameter constraint not stated in the schema: the call must reuse the account_link_id from the prior login session. The required confirmation boolean, job-id matching, and snapshot hash semantics are left entirely 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?

States a specific verb and resource: creating an amendment (수정신고) of the VAT regular filing's main report body, plus that it dispatches an XBOSS job. It is somewhat close to restating the title and does not distinguish itself from neighbors such as vat__case__create or the withholding amendment tool family, so an agent cannot tell from the text alone why this tool rather than another.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives one hard prerequisite: a prior hometax__session__login with the same account_link_id, which is genuinely useful gating. However it offers no when-to-use vs when-not-to-use guidance relative to the sibling amendment/create tools, and the closing line about '도구별 실행 내용과 기존 확인 절차' is too vague to route an agent.

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