Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 기업지원금 사업장정보 저장

work24__subsidy__application__workplace_save
Destructive

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. 고용24 기업지원금 초안에 사업장정보를 저장하고 접수번호를 받습니다. 기관에 저장하는 쓰기입니다. 같은 신청으로 다시 호출하면 초안을 하나 더 만들지 않고 기존 접수번호를 돌려줍니다. 호출마다 토큰 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__workplace_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
manager_nameNo담당자명
applicant_zipNo사업장 우편번호 (5자리)
manager_emailNo담당자 이메일 (예: manager@example.com)
programme_keyYes카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
manager_phone1No담당자 유선전화 국번 앞자리 (예: 02)
manager_phone2No담당자 유선전화 나머지 (예: 6380-5554)
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
manager_mobile1No담당자 휴대전화 앞자리 (예: 010)
manager_mobile2No담당자 휴대전화 나머지
application_yearNo신청 시작 연도
payment_bank_nameNo지원금 입금 은행명
payment_account_noNo지원금 입금 계좌번호
application_quarterNo신청 시작 분기/월 구분값
applicant_base_addressNo사업장 기본주소
business_management_noNo11-digit 고용보험 사업장관리번호. 비우면 로그인 시 저장된 값을 쓴다.
payment_account_holderNo예금주명 (사업장명과 일치해야 한다)
applicant_detail_addressNo사업장 상세주소

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is known; the description still adds real value by disclosing the 1-token cost per call, the need to create an XBOSS job, the receipt number return, and — most usefully — that re-calling with the same application is idempotent and returns the existing receipt instead of creating a second draft. It does not explain what happens to previously saved workplace fields on re-save, which is the destructive angle an agent would want.

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 prerequisite is correctly front-loaded and the idempotency note is valuable, but the closing two sentences ('순수 읽기 전용이 아닙니다', '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다') largely restate the readOnlyHint=false annotation or say nothing actionable.

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 17-parameter, no-output-schema write tool, the description covers the prerequisite, the side effect (XBOSS job creation), the cost, and the return value (receipt number), which is what an agent needs to call it. Only the destructive-overwrite semantics of re-saving workplace data remain unaddressed.

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% across all 17 parameters, so the schema carries parameter meaning on its own. The description adds nothing parameter-specific beyond repeating the account_link_id constraint that the schema already documents, so the baseline of 3 applies.

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 states a specific verb+resource: it saves workplace (사업장) information into a 고용24 subsidy application draft and returns a receipt number (접수번호). This is distinguishable from adjacent siblings such as target_save or submit by the resource named, though no sibling is named explicitly for contrast.

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?

A hard prerequisite is given up front (prior work24__auth__npki_session__login with the same account_link_id) and the repeat-call behavior is spelled out. However, there is no guidance on when to choose this over modify, target_save, or init, and no stated conditions under which it should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
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