XBOSS

홈택스 원천세 정기신고 미리보기

hometax__tax__withholding__regular_report__preview

REQUIRES prior hometax__session__login call with same account_link_id. Preview a regular-withholding draft before submission. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 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": {
      "draft_id": "<draft_id>",
      "expected_state_version": "<expected_state_version>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "hometax__tax__withholding__regular_report__preview"
  }
}

Input Schema

Name	Required	Description
`draft_id`	Yes	Draft ID returned by init
`annex_document`	No	Optional annex document payload
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`idempotency_key`	Yes	Idempotency key for safe retry
`expected_state_version`	Yes	Expected draft state version
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations, it discloses real side effects: a token is consumed per call, an XBOSS task is created and its result persisted, and the call is explicitly 'not purely read-only' despite the 'preview' name — a valuable corrective to a potentially misleading verb. What exactly gets persisted and whether it affects the draft's state version is left vague, and the phrase 'anonymous taste calls' is a translation artifact that adds confusion rather than clarity.

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

Conciseness2/5

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

The definition is front-loaded with the login precondition, but the actual purpose sentence is stranded between it and five sentences of idempotency mechanics that concern an optional parameter. It then tacks on untranslated Korean boilerplate about XBOSS tasks and token consumption that an English-language agent must parse anyway. Several sentences could be one, and the mixed-language tail does not earn its place.

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 six-parameter tool with a nested object and no output schema, the description covers authentication, cost, idempotency, and side effects reasonably well. However, it never states what a preview returns (validation result? computed tax figures?) nor how it feeds the review/submit siblings, leaving a meaningful gap for an agent deciding what to do with the result.

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 earns an extra point by disambiguating the two similarly named keys: idempotency_key (required, provider-specific, must not be altered) versus request_idempotency_key (optional, generated and reused only to recover a lost response, new key per new execution). The schema itself defers to the description for this, so the explanation carries real weight. It says nothing about annex_document or expected_state_version beyond what the schema already states.

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 second sentence gives a concrete verb and object: 'Preview a regular-withholding draft before submission,' which distinguishes it from the amendment_report and late_report preview siblings by report type. The core purpose is clear, though it is buried behind a precondition sentence and the description never explains what the preview output actually is.

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 states a hard prerequisite ('REQUIRES prior hometax__session__login call with same account_link_id') and a positional guideline ('before submission'), which is enough for an agent to place the call correctly. It does not explicitly contrast the tool with sibling steps such as requirements, review, or submit, so the agent must infer the ordering from the sibling names.

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

All XBOSS tools Inspect

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

Need Help?