XBOSS

고용24 기업지원금 대상자 저장

work24__subsidy__application__target_save

Destructive

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. target_search 가 돌려준 irno 값으로 고른 피보험자를 초안의 지원금 대상자로 지정합니다. 기관에 저장하는 쓰기이며, 초안이 작성중인 동안에는 되돌릴 수 있습니다. 호출마다 토큰 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>",
      "target_irnos": "<target_irnos>",
      "worker_type": "<worker_type>",
      "labor_contract": "<labor_contract>"
    },
    "name": "work24__subsidy__application__target_save"
  }
}

Input Schema

Name	Required	Description
`receipt_no`	Yes	민원신청접수번호 (cvplRqutRcno). workplace_save 가 발급한 값.
`worker_type`	Yes	근로자유형. 고용24 화면 필수 선택 항목이며 기관이 채워 주지 않는다. 라벨은 target_search 응답의 selection_options 에 있다.
`target_irnos`	Yes	target_search 결과의 irno 배열. 주민번호는 필요하지 않다 — 기관이 이미 아는 값을 다시 받지 않는다.
`programme_key`	Yes	카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
`labor_contract`	Yes	근로계약유형. 고용24 화면 필수 선택 항목.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`business_management_no`	No	11-digit 고용보험 사업장관리번호. 비우면 로그인 시 저장된 값을 쓴다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: one token consumed per call, an XBOSS job created and its result stored, reversibility only while the draft is in progress, and an explicit warning that this is not a pure read despite any prior lookup. That is exactly the quota and side-effect context annotations cannot carry.

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

Conciseness4/5

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

The hard prerequisite is front-loaded in the first sentence and the rest stays dense with concrete facts. Minor waste in the closing boilerplate ('기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다') and mild redundancy between '기관에 저장하는 쓰기' and '순수 읽기 전용이 아닙니다'.

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

Completeness4/5

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

For a 7-parameter, 5-required mutation with no output schema, the description covers auth prerequisite, side effects, cost, and reversibility window, which is most of what an agent needs. It omits failure behavior and any hint of what the call returns on success.

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 the baseline is 3. The description does add provenance for target_irnos (from target_search results, no resident number needed), but the remaining parameters — worker_type, labor_contract enums, account_link_id, business_management_no — are explained by the schema, not the description.

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 names a specific verb and resource ('target_search 가 돌려준 irno 값으로 고른 피보험자를 초안의 지원금 대상자로 지정') and names the sibling that supplies its input, so an agent can distinguish it from target_search or target_init without opening a schema.

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?

It states an explicit prerequisite ('REQUIRES prior work24__auth__npki_session__login call with same account_link_id') and the correct input source (irno from target_search), plus a valid operating window (draft in progress). It stops short of stating exclusions, e.g. that it cannot be used after submit or withdraw.

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?