XBOSS

상호로 사업자 찾기

opendata__comwel__name_search

공공데이터포털에 개방된 고용보험과 산재보험 가입 사업장 정보(data.go.kr 15059256)를 주기적으로 받아 둔 색인에서 상호로 사업자를 찾아 사업자등록번호, 사업장명, 주소, 성립일을 돌려줍니다. 법인과 개인사업자가 함께 오르고, 상호가 그것으로 시작하는 사업장이 먼저 옵니다. 돌려받은 사업자등록번호로 다른 조회를 이어 갈 수 있습니다. 직원 없이 혼자 운영해 보험에 가입하지 않은 사업자는 없을 수 있어, 결과가 비어 있어도 그 상호의 사업자가 없다는 뜻은 아닙니다. 별도 연동 없이 사용할 수 있습니다. 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": {
      "businessName": "<businessName>"
    },
    "name": "opendata__comwel__name_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	돌려받을 최대 행 수(선택, 기본 20).
`businessName`	Yes	찾을 상호(사업장명). 「주식회사」나 「(주)」 같은 법인 형태 표기와 띄어쓰기는 무시합니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only say readOnlyHint=false / openWorldHint=true / destructiveHint=false, and the description adds substantial context beyond that: the data is a periodically refreshed cached index (so it can be stale), prefix-matching names are ranked first, coverage is limited to insurance subscribers, and each call consumes a token and creates a stored XBOSS job so the call is not purely read-only. That side-effect disclosure is consistent with readOnlyHint=false. Points are lost for the tangled boilerplate passage about idempotency keys and the confusing 'not available to anonymous taste calls' line.

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 Korean opening is well front-loaded and information-dense: source, ordering, returns, coverage caveat, then side effects. Roughly half the text, however, is generic English boilerplate about idempotency keys and XBOSS jobs, including a duplicated key-handling instruction, an unclear 'anonymous taste calls' phrase, and a closing sentence about institutional data changes that adds little for this specific tool.

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 three-parameter search with no output schema, the description covers what is returned, how results are ordered, the freshness of the underlying index, the coverage limitation, and the non-read-only side effect. Remaining gaps are minor, such as total-count or truncation behavior when limit caps at 50 and how often the index refreshes.

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 baseline would be 3, but the description carries real weight for request_idempotency_key, whose schema entry only says 'see the tool description' — the description explains when to reuse the key (recover a lost response) versus when to mint a new one. It adds no extra detail on limit behavior or result ordering parameters, but the required businessName semantics are already fully documented in 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 names a specific verb and resource (find a business by trade name) over a precisely described index sourced from data.go.kr 15059256, and enumerates the returned fields (business registration number, workplace name, address, establishment date). It does not name any sibling tool (e.g. opendata__comwel__workplace or opendata__nts__status) to disambiguate, so it falls short of the full sibling-differentiation bar for a 5.

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 gives clear usage context: use when you have a trade name, and it explains that the returned registration number can seed a follow-up lookup, which frames it as an entry point. It also warns that empty results do not prove a business does not exist because uninsured solo operators are absent from the index. It never names an alternative tool or states an explicit when-not-to-use case.

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?