Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

사업자등록증명 신청

hometax__certificate__apply__business_registration
Destructive

REQUIRES prior hometax__session__login call with same account_link_id. Apply for Business Registration 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
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발급 매수 (서식의 선택 입력)
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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by spelling out that the action files an application with the NTS, creates a receipt record (cvaId + rcatNo), and has no cancel action. This aligns with destructiveHint=true and readOnlyHint=false and gives concrete consequence detail the annotations cannot convey.

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 and irreversibility warning, then the confirm workflow, then the token cost. Dense, imperative, and every sentence carries actionable information.

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 an irreversible, no-output-schema mutation tool with 8 optional params, the description covers the prerequisite, the irreversibility and receipt artifacts, the confirm-safety workflow, and cost. Nothing an agent needs to call it safely and correctly 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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantics on the critical confirm parameter (preview-first, never auto-confirm) that the schema alone does not convey in context. The Korean form-field parameters are left to the schema, which is acceptable given full coverage.

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+resource: 'Apply for Business Registration Certificate.' An agent can tell what it does at a glance. However, it does not distinguish itself from the near-identical sibling hometax__certificate__apply__business_registration_reissue, leaving the reissue-vs-first-application choice to inference.

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 (prior hometax__session__login with same account_link_id) and lays out the exact when-to-use workflow: call without confirm for a preview, show the user, then retry with confirm=true, never self-confirming. It also discloses the per-call token cost, so there is nothing left to infer.

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