XBOSS

표준재무제표증명 신청

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.

Input Schema

TableJSON Schema

Name	Required	Description
`bsno`	Yes	대상 사업자등록번호(숫자 10자리) (서식이 요구하는 값)
`txyr`	No	과세년도(개인, YYYY) (구분에 따라 서식이 요구하는 값)
`qrtTrt`	Yes	개인/법인 구분 코드(02 개인, 03 법인) (서식이 요구하는 값)
`adrOpYn`	No	Show address on the certificate: 'Y' or 'N'
`amtOpYn`	No	Show amount: 'Y' or 'N'
`confirm`	No	Set true ONLY after showing the preview to the user and receiving their explicit approval. Omit it on the first call to obtain the preview.
`incClCd`	No	소득구분(개인) (구분에 따라 서식이 요구하는 값)
`bsyrEndYm`	No	사업연도 종료연월(법인, YYYYMM) (구분에 따라 서식이 요구하는 값)
`resnoOpYn`	No	Show resident number: 'Y' or 'N' (forced 'N' for corporations)
`cerpIsnRqsQty`	No	Number of copies to issue (발급 매수)
`account_link_id`	No	Account 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).
`cvaDcumGranMthdCd`	No	Delivery method code (교부방법 코드)
`cvaDcumSbmsOrgnClCd`	No	Submission target code (제출처 구분코드)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026
- addedInput schema / required
```
Added value: +[
+  "bsno",
+  "qrtTrt"
+]
```
First observedSep 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses that the call files an NTS application, creates a receipt record (cvaId + rcatNo), and is irreversible with no cancel action. It also states the agent must never set confirm=true autonomously. This is exactly the behavioral context a mutation tool needs.

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-loaded with the prerequisite, then purpose, then the irreversibility warning, then the interaction workflow. Every sentence is actionable and none is filler.

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 13-parameter, non-read-only tool with no output schema, the description covers the essentials: auth prerequisite, irreversibility, side effects (NTS filing + receipt record), and the confirm gating workflow. Nothing an agent needs to invoke it safely is missing.

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 parameter behavior is already documented. The description's explanation of the confirm preview flow largely restates the schema's confirm description and adds little new per-parameter meaning (e.g., no guidance on adrOpYn/resnoOpYn interactions). Baseline 3 applies when the schema carries the load.

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?

The description names a precise verb ('Apply for') and a specific resource ('Standard Financial Statement Certificate'), which distinguishes it from the many sibling certificate-application tools (business_registration, national_tax_payment, vat_standard, tax_payment_record). An agent can identify the correct certificate type without opening the 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?

It gives strong prerequisites ('REQUIRES prior hometax__session__login call with same account_link_id') and an explicit two-step interaction pattern: call without confirm for a preview, show it to the user, then retry with confirm=true. It does not, however, name which alternative to use instead of the sibling apply_auto or apply_with_template tools, so it falls short of full when/when-not routing.

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?