Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

표준재무제표증명 신청

hometax__certificate__apply__financial_statement
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Apply for Standard Financial Statement Certificate. IRREVERSIBLE: this files an application with the NTS and a receipt record (cvaId + rcatNo) is created; there is no cancel action. Call without confirm first to get a preview, show it to the user, then retry with confirm=true. Never set confirm=true on your own. 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
bsnoYes대상 사업자등록번호(숫자 10자리) (서식이 요구하는 값)
txyrNo과세년도(개인, YYYY) (구분에 따라 서식이 요구하는 값)
qrtTrtYes개인/법인 구분 코드(02 개인, 03 법인) (서식이 요구하는 값)
adrOpYnNo주소 표시 여부(Y/N) (서식의 선택 입력)
amtOpYnNo금액 표시 여부(Y/N, 그 항목이 있는 서식에서만 반영) (서식의 선택 입력)
confirmNoSet true ONLY after showing the preview to the user and receiving their explicit approval. Omit it on the first call to obtain the preview.
incClCdNo소득구분(개인) (구분에 따라 서식이 요구하는 값)
bsyrEndYmNo사업연도 종료연월(법인, YYYYMM) (구분에 따라 서식이 요구하는 값)
resnoOpYnNo주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)
cerpIsnRqsQtyNo발급 매수 (서식의 선택 입력)
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
cvaDcumGranMthdCdNo교부방법 코드 (서식의 선택 입력)
cvaDcumSbmsOrgnClCdNo제출처 구분코드 (서식의 선택 입력)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / adrOpYn / description
      Previous value: -"Show address on the certificate: 'Y' or 'N'"New value: +"주소 표시 여부(Y/N) (서식의 선택 입력)"
    • changedInput schema / properties / amtOpYn / description
      Previous value: -"Show amount: 'Y' or 'N'"New value: +"금액 표시 여부(Y/N, 그 항목이 있는 서식에서만 반영) (서식의 선택 입력)"
    • changedInput schema / properties / cerpIsnRqsQty / description
      Previous value: -"Number of copies to issue (발급 매수)"New value: +"발급 매수 (서식의 선택 입력)"
    • changedInput schema / properties / cvaDcumGranMthdCd / description
      Previous value: -"Delivery method code (교부방법 코드)"New value: +"교부방법 코드 (서식의 선택 입력)"
    • changedInput schema / properties / cvaDcumSbmsOrgnClCd / description
      Previous value: -"Submission target code (제출처 구분코드)"New value: +"제출처 구분코드 (서식의 선택 입력)"
    • changedInput schema / properties / resnoOpYn / description
      Previous value: -"Show resident number: 'Y' or 'N' (forced 'N' for corporations)"New value: +"주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)"
  2. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
+  "bsno",
+  "qrtTrt"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond annotations: explicitly declares IRREVERSIBLE, explains a receipt record (cvaId + rcatNo) is created with no cancel action, mandates the preview-then-confirm human-in-the-loop pattern, and discloses per-call token cost. These go well beyond the destructiveHint=true annotation.

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

Conciseness5/5

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

Front-loads the prerequisite and irreversibility warning before the workflow, and every sentence earns its place. No filler; the token-cost note is terse and useful.

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 mutation tool with no output schema, the description covers prerequisites, side effects, irreversibility, human-approval workflow, and cost. An agent has everything needed to call it safely and correctly.

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 coverage is 100%, and the confirm semantics in the description largely mirror the schema's own confirm description. The description reinforces the workflow but adds little parameter-level meaning beyond what the schema already documents for the 13 fields.

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 ('Apply for') and a precisely named resource ('Standard Financial Statement Certificate'), which cleanly distinguishes it from sibling certificate tools like business_registration or national_tax_payment. An agent can identify the target document 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 Guidelines4/5

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

Gives explicit prerequisites (prior hometax__session__login with same account_link_id) and a clear two-step workflow: call without confirm for a preview, then retry with confirm=true. It doesn't compare against sibling apply variants (e.g. apply_auto) to help choose the right certificate path, so it's clear but not fully routing.

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