XBOSS

고용24 기업지원금 신청 필요입력 안내

work24__subsidy__application__requirements

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. List what the applicant must supply before any write: institution-provided values, customer-required fields, registered payment accounts, and how attachments are procured (the document list itself is issued by draft_validate, keyed by 접수번호). Read-only — call this before workplace_save. 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>"
    },
    "name": "work24__subsidy__application__requirements"
  }
}

Input Schema

Name	Required	Description
`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

Behavior2/5

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

The description contradicts itself and the annotations: it opens with 'Read-only — call this before workplace_save' while annotations declare readOnlyHint=false, and only in the closing Korean boilerplate does it concede '이 호출은 순수 읽기 전용이 아닙니다' (this call is not purely read-only). It does add genuinely useful behavior detail — one token consumed per call, an XBOSS job created and its result stored — but an agent skimming the leading 'Read-only' claim could wrongly treat it as side-effect free.

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 purpose statement is front-loaded but is preceded by the auth prerequisite and followed by a long generic idempotency paragraph plus untranslated Korean boilerplate, so the core message is diluted. Every block carries some content, but the idempotency text reads as template copy reusable across many tools rather than tool-specific guidance.

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?

With no output schema, the description does sketch the returned categories and the prerequisite, token cost, and sibling sequencing, which covers most of what an agent needs. However, the mixed read-only messaging leaves the agent uncertain about side effects, and the return shape (e.g., whether values are keyed per field) is only loosely implied.

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 would be 3; the description earns extra by explaining that request_idempotency_key must be generated before the first request, reused only to recover a lost response, replaced for a new execution, unavailable to anonymous calls, and distinct from a provider-specific idempotency_key. It also ties account_link_id to the login session. It adds little on business_management_no beyond the schema.

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 gives a specific verb and resource: 'List what the applicant must supply before any write', and enumerates the categories returned (institution-provided values, customer-required fields, registered payment accounts, attachment procurement). It also distinguishes this tool from sibling draft_validate, which is the tool that issues the document list keyed by 접수번호.

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 a hard prerequisite ('REQUIRES prior work24__auth__npki_session__login call with same account_link_id') and an explicit sequencing rule ('call this before workplace_save'), plus routing to draft_validate for the document list. What's missing is an explicit when-not-to-use case or a statement of what happens if called after workplace_save, but the practical guidance is strong.

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?