Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

증명서 자동 신청

hometax__certificate__apply_auto
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Apply for a certificate using the logged-in taxpayer's own details. 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
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.
resnoOpYnNo주민등록번호 표시 여부(Y/N, 법인은 N 고정) (서식의 선택 입력)
cerpIsnRqsQtyNo발급 매수 (서식의 선택 입력)
cert_templateNoCertificate template slug. One of: cert_gukse_wannap 국세완납증명 / cert_napse_sasil 납세사실증명 / cert_bugase_gwase_pyojun 부가가치세과세표준증명 / cert_saeopja_deungrok_jeungmyeong 사업자등록증명 / cert_hyupeop_sasil 휴업사실증명 / cert_pyojun_jaemu_jepyo 표준재무제표증명 / cert_pyepeop_sasil 폐업사실증명 / cert_saeopja_jaebalgup 사업자등록증 재발급 / cert_sodeuk_geumaeg_jeungmyeong 소득금액증명. Defaults to cert_gukse_wannap when omitted; any other value is refused before the NTS is contacted.
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).
use_company_tinNotrue (default) uses the corporate TIN; false uses the representative's personal TIN.
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. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already mark this as destructive and non-read-only, and the description adds substantial context beyond them: the NTS filing creates a receipt record, there is no cancel action, and each call consumes one token. This makes the irreversible side effects and confirmation workflow fully transparent.

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 session prerequisite and the IRREVERSIBLE warning, then gives the confirm workflow and token cost in compact sentences. Every sentence carries actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the critical context for a destructive filing tool: authentication prerequisite, irreversibility, no-cancel behavior, preview/confirm protocol, and token cost. It is nearly complete, though it could mention the specialized certificate-application siblings to help route the agent.

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 10 parameters are documented in the schema itself. The description reinforces the confirm parameter's two-step preview behavior and the account_link_id prerequisite but does not add much parameter meaning beyond the schema baselines.

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?

States a specific verb and resource: apply for a certificate using the logged-in taxpayer's own details. It is clear that this files an NTS application, but it does not differentiate itself from specialized siblings such as hometax__certificate__apply__business_registration or apply_with_template.

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?

Explicitly requires a prior hometax__session__login with the same account_link_id and mandates a preview-first flow before confirm=true. It strongly warns never to set confirm=true autonomously, but it does not explain when to choose this generic auto tool over the specialized certificate-application siblings.

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