Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용보험 및 산재보험 가입 사업장 조회

opendata__comwel__workplace

공공데이터포털에 개방된 고용보험과 산재보험 가입 사업장 정보(data.go.kr 15059256)를 사업자등록번호로 조회합니다. 사업장명, 보험 구분, 보험가입구분, 성립일자, 상시인원, 업종, 우편번호, 주소를 사업장(적용 단위)마다 한 행으로 돌려주고 summary 에 보험별 사업장 수와 상시인원 합계를 담습니다. 결과가 비어 있어도 미가입 확인서는 아닙니다. 별도 연동 없이 사용할 수 있습니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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": {
      "bizno": "<bizno>"
    },
    "name": "opendata__comwel__workplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
biznoYes사업자등록번호 10자리(하이픈 허용).
pageNoNo페이지 번호(선택, 기본 1).
insuranceNo보험 구분(선택, 기본 all). industrial 은 산재보험, employment 는 고용보험 행만 돌려줍니다.
numOfRowsNo한 페이지 행 수(선택, 기본 100).
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
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

A4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description goes well beyond them by disclosing per-call token consumption, XBOSS job creation and result storage, and explicitly warning that the call is not purely read-only despite reading provider data. It also covers file artifacts (xlsx, 15-minute download links, 7-day retention), the recovery path via xdata__job__result, recovery_receipt handling for anonymous results, and idempotency-key reuse semantics — behavior an agent cannot infer from 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and return-shape information is front-loaded and efficient, but the file/receipt/idempotency block is long and reads as boilerplate that outweighs the one-line domain description. Details such as the receipt not being repairable by signing up are relevant but could be compressed.

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?

With no output schema, the description carries the burden of describing return values and does so by listing per-row fields plus the summary counts and totals, and it flags the empty-result interpretation pitfall. The main residual gap is paging behavior when results exceed numOfRows, which the description does not address.

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%, so the schema already explains bizno format, insurance enum values, paging, and output_formats. The description adds only the summary aggregation semantics tied to the insurance parameter, without extra syntax or format detail, so the baseline of 3 applies.

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 first sentence names a specific verb and resource (고용보험/산재보험 가입 사업장 조회) and pins the lookup key to 사업자등록번호, which implicitly separates it from the name-based sibling opendata__comwel__name_search. It also enumerates the returned fields and the summary aggregation, so an agent knows exactly what it gets.

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?

It gives one genuinely useful usage caveat — an empty result is not proof of non-enrollment — and states no separate integration is needed. However, it never routes the agent to an alternative (e.g. the name-based search sibling) when only a company name is available, and gives no guidance on paging or when to add the insurance filter, so selection guidance is only implied.

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