Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 기업지원금 제출 전 확인

work24__subsidy__application__draft_validate

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. 초안을 실제 화면과 대조해 첨부 서류 목록과 제출할 수 있는지를 돌려줍니다. 제출은 하지 않으며, submit 전에 반드시 거치는 확인입니다. 일부 사업은 화면을 옮길 때 초안이 저장되며, 저장됐는지는 결과의 safety.save_executed 가 알려 줍니다. 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>",
      "receipt_no": "<receipt_no>"
    },
    "name": "work24__subsidy__application__draft_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_noYes민원신청접수번호 (cvplRqutRcno). workplace_save 가 발급한 값.
programme_keyYes카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
business_management_noNo11-digit 고용보험 사업장관리번호. 비우면 로그인 시 저장된 값을 쓴다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes further by warning the call is not purely read-only, that it consumes one token per call, that it creates an XBOSS job and stores the result, and that some programmes persist the draft on navigation with safety.save_executed reporting it. These are real behavioral disclosures beyond the structured fields. The garbled 'anonymous taste calls' clause is noise but not contradictory.

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 properly front-loaded and the validation role follows immediately, but the text then drifts into lengthy idempotency boilerplate and confusing phrasing such as 'anonymous taste calls'. Language switches between Korean and English mid-paragraph, adding reading cost without adding selection signal.

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 five-parameter mutating check with a fully described schema and a prior-login dependency, the description covers prerequisite, side effects, cost, and partial return-value information (safety.save_executed). Without an output schema it could say more about the full return shape, but nothing needed to call it correctly is missing.

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. The description nonetheless adds meaning: it ties account_link_id to the login prerequisite and elaborates the idempotency_key lifecycle (generate before first request, reuse only for lost-response recovery, new key per execution, distinct from a provider-specific key). It does not add anything about receipt_no or programme_key beyond the schema.

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 and resource: it compares the draft against the actual screen and returns the attachment list plus whether submission is possible, and explicitly says it does not submit. That distinguishes it from the sibling submit tool. The core purpose is clear, though it is buried under mixed Korean/English boilerplate.

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 (a prior work24__auth__npki_session__login call with the same account_link_id) and positions itself as a mandatory gate before submit. It does not contrast itself with adjacent siblings such as requirements or history, so alternative selection guidance is incomplete.

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