XBOSS

고용24 기업지원금 신청 진입

work24__subsidy__application__init

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. 조회만 합니다. 고용24 기업지원금 신청 화면에 들어가 그 사업의 사전진단 판정을 확인하고 화면의 입력 항목 구성을 돌려줍니다. 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__init"
  }
}

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

B3.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) the description discloses meaningful behavior: the NPKI session prerequisite, a per-call token cost, creation of an XBOSS task with stored processing results, and explicit idempotency recovery semantics. It also correctly warns that the call is not purely read-only, though the earlier sentence '조회만 합니다' creates internal tension that could momentarily mislead a skimming agent.

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 purpose statement is buried in the middle of mixed-language boilerplate that spans prerequisities, four sentences of idempotency policy, token accounting, and a generic sentence about institutional data changes. Several sentences read as templated text copied across tools and do not earn their place, and the front-loading is weak.

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 say what comes back at a high level (pre-diagnosis verdict plus screen input-field composition), and it covers the auth prerequisite and idempotency. However it never clarifies whether this call opens a server-side draft session or how its returned field composition relates to the sibling save/submit tools, which is the key missing piece for a flow-entry tool.

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 already 100%, so the baseline is 3; the description raises it by explaining how request_idempotency_key must be generated and saved before the first request and reused only to recover from a lost response. It also ties account_link_id to the login prerequisite ('same account_link_id'). The trailing 'anonymous taste calls' caveat is confusing noise rather than added meaning.

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 Korean purpose sentence names a specific action and resource: enter the 고용24 기업지원금 신청 screen, verify that project's 사전진단 verdict, and return the screen's input-field composition. That is a real verb+resource+return statement, not a restatement of the name. It does not differentiate from near siblings such as subsidy__application__requirements or __target_init, which likely also expose application-screen prerequisites.

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

Usage Guidelines2/5

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

The only usage guidance is a precondition: a prior work24__auth__npki_session__login call with the same account_link_id. There is no statement of when to call this versus requirements, target_init, or draft_validate, and no when-not guidance. An agent must still infer its place in the application flow.

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?