XBOSS

사업자등록증명 발급

gov24__business_registration_certificate__issue

Destructive

REQUIRES prior gov24__session__login call with same account_link_id. 사업자등록증명을 발급하고 내려받는 링크를 돌려줍니다. privacy_disclosure 로 주민등록번호를 표시할지 정합니다. pre_consent 는 true 여야 합니다. 이 도구는 기관의 기록을 바꿉니다. 첫 호출은 실행되지 않고, 전송할 내용의 미리보기와 1회용 confirmation_token 을 돌려줍니다(오류 WRITE_CONFIRMATION_REQUIRED). 그 미리보기를 사용자에게 그대로 보여 줍니다. 사용자가 동의한 뒤에만 같은 인자에 그 confirmation_token 을 더해 다시 호출합니다. 사용자의 동의 없이 토큰을 넣지 않습니다. 인자를 하나라도 바꾸면 토큰은 무효가 됩니다. 그때는 토큰 없이 호출해 새 미리보기를 받습니다. Files: the document the institution issued, unchanged, as PDF, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "certificate_purpose": "<certificate_purpose>",
      "receive_method": "<receive_method>",
      "pre_consent": "<pre_consent>"
    },
    "name": "gov24__business_registration_certificate__issue"
  }
}

Input Schema

Name	Required	Description
`member_type`	No	Optional. Member kind.
`pre_consent`	Yes	Must be true. Confirms the prior consent.
`receive_method`	Yes	Delivery code.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.
`privacy_disclosure`	No	N hides the resident registration number on the document.
`certificate_purpose`	Yes	Stated purpose for the certificate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The annotations (readOnlyHint=false, destructiveHint=true) are fully backed up by the description: it says outright that the tool changes the institution's records and is not pure read-only, and that each call consumes one token. Beyond that, it discloses details the annotations cannot carry: the 15-minute download_url lifetime, 7-day file retention, one-time token expiry and invalidation rules, and the irrecoverable nature of the recovery_receipt.

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

Conciseness3/5

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

The prerequisite is front-loaded, which is correct, but the body is long and mixes Korean, English, and boilerplate about XBOSS jobs and token consumption. Some sentences feel like appended system text rather than tool documentation, so the core call sequence is buried.

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, multi-step, two-phase-commit tool there is no output schema, but the description still covers the return shape (artifacts[] with download_url), the confirmation-token lifecycle, and the file-retention and recovery behavior. Nothing critical for calling it 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 coverage is 100%, so the baseline is 3; the description earns one more point by adding meaning the schema lacks, such as what privacy_disclosure='N' hides (the resident registration number on the document) and why pre_consent must be true. certificate_purpose and receive_method still get no extra explanation beyond their schema text.

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?

The description states a specific verb and resource: it issues a 사업자등록증명 and returns a link for downloading it, then explains what artifacts[] contains. It does not, however, name any of the many sibling certificate tools (hometax__certificate__apply__business_registration, fourinsure__b1__certificate__issue_fact__confirm, etc.) or explain how this tool differs from them, so an agent cannot choose between them from this text alone.

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 states prerequisites explicitly (a prior gov24__session__login with the same account_link_id, pre_consent=true), the mandatory confirmation handshake, and what to do at each point: show the preview, get consent, then re-call with the token, and drop the token whenever an argument changes. It also routes the agent to xdata__job__result with the job_id for expired links and explains the recovery_receipt fallback for anonymous results.

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?