XBOSS

사업장 성립신고 초기화

fourinsure__b1__business_establishment__init

REQUIRES prior fourinsure__session__login call with same account_link_id. Initialize business establishment declaration. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fourinsure__b1__business_establishment__init"
  }
}

Input Schema

Name	Required	Description
`cvrc_no`	No	FourInsure application receipt number (cvrcNo). Leave empty for a new lookup; pass it to reference an existing application.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds that each call consumes one token, creates an XBOSS job and persists the result, and that it is "not pure read-only" regardless of whether the institution source is queried. It stops short of naming what state the initialization creates or how to recover or cancel an initialized session.

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

Conciseness2/5

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

The name-defining clause is buried behind a capitalized prerequisite and several sentences of idempotency boilerplate with redundant restatement ("Without it, calling again remains a new request"). The bilingual split between English and Korean also repeats the same concepts, inflating length without adding information.

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

Completeness3/5

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

Auth, cost, side effects and idempotency are covered, but with no output schema the description never says what an initialization returns (a handle, session reference, or job id) or which tool to call next. For a multi-step declaration flow, that leaves the agent's critical next step unstated.

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 more by explaining the idempotency key's reuse semantics and warning that a provider-specific idempotency_key is a different field that must not be altered. It adds no semantics for cvrc_no beyond what the schema already states.

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?

"Initialize business establishment declaration" gives a specific verb and resource, and the Korean sentence adds that an XBOSS job is created per call. It does not distinguish this from the sibling draft_validate or explain what the initialization produces, so an agent must infer the workflow stage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite is explicit ("REQUIRES prior fourinsure__session__login call with same account_link_id") and the idempotency key rules are spelled out (reuse only to recover a lost response, new key for a new execution). However there is no guidance on when to choose this over sibling init/draft_validate tools or what should follow the call.

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?