XBOSS

소득금액증명 신청

hometax__certificate__apply__income_statement

Destructive

REQUIRES prior hometax__session__login call with same account_link_id. 소득금액증명(Certificate of Income) 신청을 기관에 접수합니다. 개인과 개인사업자만 신청할 수 있습니다. 법인은 신청할 수 없으며 기관 화면이 거절합니다. 되돌릴 수 없습니다. 접수하면 기관에 접수 기록(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": {
      "txnrmEndYm": "<txnrmEndYm>",
      "txnrmStrtYm": "<txnrmStrtYm>"
    },
    "name": "hometax__certificate__apply__income_statement"
  }
}

Input Schema

Name	Required	Description
`adrOpYn`	No	주소 표시 여부(Y/N) (서식의 선택 입력)
`resnoOpYn`	No	주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)
`txnrmEndYm`	Yes	과세기간 종료년월(YYYYMM, 예: 202412) (서식이 요구하는 값)
`txnrmStrtYm`	Yes	과세기간 시작년월(YYYYMM, 귀속연도 전체 예: 202401) (서식이 요구하는 값)
`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.5/5.0

Behavior4/5

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

Well beyond the annotations: it discloses that the submission is irreversible, leaves a permanent record (cvaId, rcatNo), has no cancel function, creates an XBOSS task and stores a processing result, and that one token is consumed per call. The annotations already flag destructiveHint=true and readOnlyHint=false, so the description's job is to add the specifics, which it largely does; only the response payload shape of the preview is left implicit.

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 and the confirmation protocol are front-loaded, which is good, but the closing lines are padded and partly redundant — '이 도구는 기관의 기록을 바꿉니다' restates destructiveHint, and '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다' is boilerplate that adds nothing. The XBOSS-task sentence is dense and slightly garbled, weakening the otherwise strong structure.

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?

There is no output schema, and the description compensates by explaining what the first call returns (a preview plus a one-time confirmation_token, signalled by WRITE_CONFIRMATION_REQUIRED) and what must be shown to the user. For a destructive 9-parameter tool, the prerequisites, consent gate, and irreversibility are all covered.

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 real parameter behavior not in the schema: the confirmation_token is single-use, expires in 10 minutes per the schema yet is invalidated immediately by changing any argument, and account_link_id must match the earlier login session. Those lifecycle rules govern how the two required parameters interact, which the field descriptions alone do not convey.

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 (신청/접수 = submit an application) and a specific resource (소득금액증명 / Certificate of Income), and adds the eligibility scope (individuals and sole proprietors only; corporations rejected by the institution screen). An agent can distinguish this from sibling certificate applications such as financial_statement or business_registration without opening any 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?

Explicitly states the prerequisite (a prior hometax__session__login call with the same account_link_id), the eligibility gate (no corporations), and the exact two-step invocation protocol: first call returns a preview, show it verbatim, obtain user consent, then re-call with the confirmation_token. It also covers the failure branch — any changed argument invalidates the token and requires a fresh preview call.

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?