Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

기업개요 조회

opendata__fsc__corp_outline

공공데이터포털에 개방된 법인 기업개요(data.go.kr 15043184)를 조회합니다. 상호(corpNm) 또는 법인등록번호(crno) 또는 사업자등록번호(bizno) 가운데 하나 이상을 주면 법인명, 사업자등록번호, 법인등록번호, 설립일자, 업종, 소재지, 종업원 수, 결산 월, 상장 시장 등을 돌려줍니다. 한 법인의 행이 여럿이면 개방 시점이 다른 기록이고 current 가 가장 최근 것입니다. 개인사업자는 이 자료에 없습니다. 별도 연동 없이 사용할 수 있습니다. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opendata__fsc__corp_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
crnoNo법인등록번호 13자리(하이픈 허용). 세 입력 가운데 하나 이상.
biznoNo사업자등록번호 10자리(하이픈 허용). 세 입력 가운데 하나 이상.
corpNmNo법인 상호(부분 일치로 검색). 세 입력 가운데 하나 이상.
pageNoNo페이지 번호(선택, 기본 1).
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

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 the description is consistent and adds real context: each call consumes one token, a backend XBOSS job is created and its result stored, and the call is explicitly "not purely read-only" even though the source lookup is a read. It further discloses artifact lifetimes (download_url valid 15 minutes, files kept 7 days), the private recovery_receipt rules for anonymous results, and idempotency-key reuse semantics. The value is genuine but partly diluted by generic platform boilerplate repeated verbatim across tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The purpose and return-field sentences at the front are excellent and well ordered. But roughly two thirds of the text is generic platform boilerplate about file retention, anonymous recovery receipts, and idempotency keys that repeats schema text and is largely irrelevant to selecting this lookup tool. The signal-to-noise ratio is poor for a call whose core behavior takes two sentences to convey.

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 explaining return values and does so by enumerating the result fields and clarifying that multiple rows represent different release snapshots, with "current" marking the latest. It also covers the optional Excel export and the recovery path for expired links. What remains thin is pagination/volume behavior, though the schema's pageNo and numOfRows bounds partly compensate.

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 documents lengths, hyphen tolerance, partial matching for corpNm, pagination bounds, and the one-of-three identifier rule. The description restates the identifier set and the output_formats/artifacts behavior without adding format, validation, or precedence details beyond the schema. Baseline 3 is correct where the schema does the heavy lifting.

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: look up the corporate overview dataset (data.go.kr 15043184) by corpNm, crno, or bizno, and enumerates the fields returned (name, business number, incorporation date, industry, location, employees, fiscal month, listing market). It also excludes sole proprietorships ("개인사업자는 이 자료에 없습니다"), which implicitly separates it from individual-business siblings such as nts__status. It stops short of naming a concrete alternative tool, so it is clear but not fully differentiated.

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 the condition for use — supply at least one of three identifiers — and one explicit exclusion (individual businesses are not covered), plus a note that no separate integration or subscription is needed. It also routes the agent to xdata__job__result when a download link has expired. It never names an alternative data source for the excluded sole-proprietor case, so the guidance is clear but not exhaustive.

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