XBOSS

부가가치세과세표준증명 신청

hometax__certificate__apply__vat_standard

Destructive

REQUIRES prior hometax__session__login call with same account_link_id. 부가가치세과세표준증명(Certificate of VAT Tax Base) 신청을 기관에 접수합니다. 되돌릴 수 없습니다. 접수하면 기관에 접수 기록(cvaId, rcatNo)이 남으며 취소 기능이 없습니다. 이 도구는 기관의 기록을 바꿉니다. 첫 호출은 실행되지 않고, 전송할 내용의 미리보기와 1회용 confirmation_token 을 돌려줍니다(오류 WRITE_CONFIRMATION_REQUIRED). 그 미리보기를 사용자에게 그대로 보여 줍니다. 사용자가 동의한 뒤에만 같은 인자에 그 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": {
      "endYm": "<endYm>",
      "strtYm": "<strtYm>"
    },
    "name": "hometax__certificate__apply__vat_standard"
  }
}

Input Schema

Name	Required	Description
`endYm`	Yes	조회 종료 연월(YYYYMM) (서식이 요구하는 값)
`strtYm`	Yes	조회 시작 연월(YYYYMM) (서식이 요구하는 값)
`adrOpYn`	No	주소 표시 여부(Y/N) (서식의 선택 입력)
`resnoOpYn`	No	주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)
`cerpIsnRqsQty`	No	발급 매수 (서식의 선택 입력)
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`cvaDcumGranMthdCd`	No	교부방법 코드 (서식의 선택 입력)
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.
`cvaDcumSbmsOrgnClCd`	No	제출처 구분코드 (서식의 선택 입력)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Far exceeds what the annotations convey: it discloses irreversibility, that an institutional record (cvaId, rcatNo) is created with no cancellation path, that the first call is a dry run returning a preview plus one-time token under WRITE_CONFIRMATION_REQUIRED, that the token is single-use and 10-minute scoped, and that an XBOSS job is created per call. It also explicitly warns that despite reading source data the call is not purely read-only, and it tells the agent to show the preview and obtain user consent before supplying the token.

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 correctly, with the prerequisite first, then purpose, then irreversibility, then the confirmation protocol. A few sentences are redundant boilerplate (the repeated statements that this is not read-only and the closing line about per-tool execution rules), which keeps it from a 5.

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 write tool with no output schema, it covers everything an agent needs: prerequisite auth, side effects, irreversibility, the preview/consent protocol, token lifetime and invalidation rules, and what the first call returns. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all nine parameters including confirmation_token and account_link_id are already documented in the schema; the description adds only reinforcement of the token's role in the retry call. It contributes no extra meaning for the form fields (endYm, strtYm, adrOpYn, resnoOpYn, etc.), so the baseline of 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?

Names the specific certificate (부가가치세과세표준증명 / Certificate of VAT Tax Base) and the action (신청, submission to the institution), which cleanly separates it from the sibling certificate tools such as business_registration or income_statement. The verb+resource+scope are all stated in the first two sentences.

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?

States a hard prerequisite (a prior hometax__session__login call with the same account_link_id) and gives precise procedural guidance for the two-step confirmation flow, including what to do when arguments change. It does not name which sibling tool to use for other certificate types, so routing guidance is implied rather than explicit.

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?