XBOSS

고용24 기업지원금 대상자정보 단계 진입

work24__subsidy__application__target_init

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. 이미 있는 초안의 대상자정보 단계에 들어가 그 입력 항목 구성을 돌려줍니다. workplace_save 가 준 접수번호(receipt_no)가 필요합니다. 제출은 하지 않습니다. 일부 사업은 화면을 옮길 때 초안이 저장되며, 저장됐는지는 결과의 safety.save_executed 가 알려 줍니다. 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

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": {
      "programme_key": "<programme_key>",
      "receipt_no": "<receipt_no>"
    },
    "name": "work24__subsidy__application__target_init"
  }
}

Input Schema

Name	Required	Description
`receipt_no`	Yes	민원신청접수번호 (cvplRqutRcno). workplace_save 가 발급한 값.
`programme_key`	Yes	카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`business_management_no`	No	11-digit 고용보험 사업장관리번호. 비우면 로그인 시 저장된 값을 쓴다.
`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.7/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description is not carrying the safety burden alone. It nonetheless adds behavior the annotations cannot express: moving screens may silently save the draft in some programs, and result.safety.save_executed reports whether that happened, plus the one-token-per-call cost and XBOSS task creation. The generic idempotency-key boilerplate and the repeated 'not purely read-only' disclaimer add bulk without new specifics.

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 critical dependency (prior login + receipt_no) is correctly front-loaded, and the no-submit and save_executed facts are high value. However, roughly half the text is generic boilerplate about request_idempotency_key, token consumption, and XBOSS task creation, and the language shifts between Korean and English mid-paragraph. Redundancy between '제출은 하지 않습니다' and '순수 읽기 전용이 아닙니다' costs further space.

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?

Prerequisites, side effects, and the no-submission guarantee are covered, and the mention of result.safety.save_executed partially compensates for the absent output schema. What remains thin is the return value itself: the tool promises the input-item composition of the step but never characterizes that structure, and there is no output schema to fill the gap. For a step-init tool whose entire payload is a returned structure, that is a visible hole.

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 every parameter already carries its own explanation, which sets the baseline at 3. The description reinforces that receipt_no comes from workplace_save and ties account_link_id to the login call, but adds no syntax, format, or validation meaning beyond the schema. There is no compensating value here that would justify a 4.

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 names a specific action and resource: entering the 대상자정보 (target-person info) step of an existing draft and returning that step's input-item composition, and it explicitly states it does not submit. That distinguishes it from submit and from a fresh application init, though the sibling names themselves are never used. The purpose survives the mixed Korean/English phrasing but is not stated as crisply as a 5 would require.

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?

Two concrete preconditions are given: a prior work24__auth__npki_session__login call with the same account_link_id, and a receipt_no produced by workplace_save. The phrase '이미 있는 초안의' (an already-existing draft) implicitly scopes use to resume-a-draft scenarios. It stops short of naming the alternative tool to call when no draft exists, which is the only reason this is not a 5.

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?