Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 기업지원금 첨부 파일 삭제

work24__subsidy__application__attachment_delete
Destructive

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. 고용24 기업지원금 초안에 첨부된 파일 하나를 삭제합니다. 파일은 draft_validate 가 알려 주는 file_id 로 지정합니다. 초안이 작성중일 때만 됩니다. 사용자가 동의한 뒤에만 보내는 confirm 이 필요합니다. 다시 읽은 첨부 목록에 그 파일이 없을 때만 삭제된 것으로 확인합니다. 이 도구는 기관의 기록을 바꿉니다. 첫 호출은 실행되지 않고, 전송할 내용의 미리보기와 1회용 confirmation_token 을 돌려줍니다(오류 WRITE_CONFIRMATION_REQUIRED). 그 미리보기를 사용자에게 그대로 보여 줍니다. 사용자가 동의한 뒤에만 같은 인자에 그 confirmation_token 을 더해 다시 호출합니다. 사용자의 동의 없이 토큰을 넣지 않습니다. 인자를 하나라도 바꾸면 토큰은 무효가 됩니다. 그때는 토큰 없이 호출해 새 미리보기를 받습니다. 호출마다 토큰 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>",
      "file_id": "<file_id>",
      "confirm": "<confirm>"
    },
    "name": "work24__subsidy__application__attachment_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes되돌릴 수 없는 처리에 대한 명시 확인. true 가 아니면 거부된다.
file_idYes지울 파일의 file_id. draft_validate 의 documents[].attached_files[].file_id 값.
receipt_noYes민원신청접수번호 (cvplRqutRcno). workplace_save 가 발급한 값.
programme_keyYes카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
confirmation_tokenNo첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.
business_management_noNo11-digit 고용보험 사업장관리번호. 비우면 로그인 시 저장된 값을 쓴다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the destructiveHint=false/readOnly=false annotations: it discloses the two-phase preview→confirmation_token flow, the WRITE_CONFIRMATION_REQUIRED error, 10-minute one-time token expiry, token invalidation if any argument changes, and the rule that deletion is only confirmed when a re-read attachment list no longer shows the file. It also states the call mutates institutional records and spawns an XBOSS job, which an agent could not infer from the annotations alone.

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?

Front-loads the auth prerequisite, then the action, then the token protocol, which is the right order for an agent. Some repetition (consent warnings stated three ways) and a generic tail about XBOSS job creation and 기관 데이터 변경 add bulk without new guidance for calling the tool.

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

Completeness5/5

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

For a destructive, state-gated mutation with 7 parameters and no output schema, the description covers everything an agent needs: authentication prerequisite, draft-state precondition, identifier source, the two-call confirmation protocol, and how to verify success. Nothing material is left to inference.

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 is 3, but the description adds real meaning: it ties file_id to draft_validate's documents[].attached_files[], requires confirm to reflect explicit user consent, and explains the confirmation_token lifecycle (obtained on the first call, replayed with identical args). It does not add much on receipt_no or 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?

States a specific verb and resource (delete one attached file from a 고용24 subsidy draft) together with its scope (one file, draft in progress only). It also names the sibling that supplies the identifier (draft_validate's file_id), so the agent can distinguish it from application-level delete and from draft_validate 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?

Gives strong when-to-use conditions: requires a prior work24__auth__npki_session__login with the same account_link_id, works only while the draft is 작성중, and file_id must come from draft_validate. It never names a sibling to use instead, e.g. that application__delete removes the whole application rather than one attachment, so the 'alternatives' element is missing.

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