Skip to main content
Glama

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

증명서 템플릿 신청

hometax__certificate__apply_with_template
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Apply for a certificate with an explicitly chosen template. 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
NameRequiredDescriptionDefault
adrOpYnNoShow address on the certificate: 'Y' or 'N'
amtOpYnNoShow amount: 'Y' or '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.
resnoOpYnNoShow resident number: 'Y' or 'N' (forced 'N' for corporations)
cerpIsnRqsQtyNoNumber of copies to issue (발급 매수)
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).
cvaDcumGranMthdCdNoDelivery method code (교부방법 코드)
cvaDcumSbmsOrgnClCdNoSubmission target code (제출처 구분코드)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true), the description discloses that the action is irreversible, files an application with the NTS, and creates a receipt record. It also warns about the no-cancel nature, which is critical for a destructive operation. This adds substantial behavioral context.

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?

Three concise sentences that front-load the most critical information (login requirement, irreversibility) before the usage flow. No wasted words; every sentence adds essential guidance.

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 9-parameter tool with no output schema, the description covers the prerequisites (login), side effects (irreversible, receipt creation), and the confirm workflow. It also mentions the receipt identifiers (cvaId, rcatNo) for the agent's awareness. Nothing critical is missing.

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. The description adds value by linking account_link_id to the login requirement and explaining the confirm parameter's role in the preview/confirm flow. While the schema already documents parameters well, the description reinforces the critical confirm semantics and the template selection context.

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 clearly states the tool's purpose: applying for a certificate with an explicitly chosen template. It distinguishes this from generic auto-apply and specific certificate types (like business registration) by emphasizing template selection, making it easy for an agent to know when to use this tool.

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?

It explicitly requires a prior login with the same account_link_id, and provides a precise two-step workflow: call without confirm to get a preview, then retry with confirm=true after user approval. It also gives a clear prohibition ('Never set confirm=true on your own'), which is actionable guidance for safe usage.

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