Skip to main content
Glama

기업 종합 프로필

company_info_pack__profile_v1__generate

사업자등록번호 하나로 상태, 위험, 고용, 재무, 사업장 다섯 축을 한 번에 조회해 한 장으로 모아 줍니다. 조각 열하나(사업자 상태와 진위, 공공조달 제재, 건설업 행정처분, 환경 제재, 기업개요, 고용보험과 산재보험 가입 사업장, 국민연금 가입 사업장, 재무 요약, 사업장 건물, 사업장 건물 실거래)가 우리 플랫폼 키로 돌아 account_link_id 와 인증서가 필요 없습니다. axes 로 축을 고르면 그 축의 조각이 필수가 되고, 비우면 사업자 상태만 필수이며 나머지는 조회된 만큼 담고 포함되지 않은 조각의 사유를 warnings 와 axes 의 notes_ko 에 적습니다. 사업자 진위확인은 start_dt 와 p_nm 을 함께 보낼 때만 포함되고, 건설업 행정처분 기간을 비우면 최근 1년입니다. 비어 있는 제재 결과를 제재가 없다는 뜻으로 읽지 마세요. If computed is null the result could not be assembled: read computed_error for the reason and do not present the result as complete. Two shapes carry that case: this envelope with partial set to true (we fetched everything - the legs hold it - but could not calculate), or an error whose data carries the same envelope. partial is true whenever the result is incomplete, whether a leg failed or the calculation did. Files: a document generated from this result, as PDF 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 pack_run_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. 호출마다 토큰 9소진 요청 처리 시 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": "company_info_pack__profile_v1__generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
axesNo필수로 받을 축 목록. status 는 상태, risk 는 위험, employment 는 고용, finance 는 재무, premises 는 사업장. 비우면 상태 축의 사업자 상태만 필수이고 나머지는 선택이다
p_nmNo대표자명. start_dt 와 함께 보내면 사업자 진위확인이 포함된다
biznoYes사업자등록번호 10자리. 바깥 정본이라 모든 조각이 이 값으로 돈다
eDateNo건설업 행정처분 조회 종료일 YYYYMMDD. 시작일과 함께 비우면 오늘(한국 시각)
endYmNo사업장 건물 실거래 조회의 마지막 달 YYYYMM(선택). 비우면 이번 달(한국 시각)부터 거슬러 최근 12개월
sDateNo건설업 행정처분 조회 시작일 YYYYMMDD. 종료일과 함께 비우면 종료일 기준 1년 전
addressNo사업장 주소(선택, 한글). 비우면 공개 자료의 소재지로 찾고, 찾지 못하면 사업장 축을 지금 못 봄으로 두고 주소를 적어 달라고 안내한다
start_dtNo개업일자 YYYYMMDD. p_nm 과 함께 보내면 사업자 진위확인이 포함된다
corp_nameNo상호(선택). 건설업 행정처분 대조에 쓴다
output_formatsNoOptional. Also return this result as a file (PDF) in artifacts[] of the result. Omit it for data only.
idempotency_keyNo바깥 멱등 키(선택). 조각의 키는 이 값에서 결정적으로 만든다

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, and the description corroborates and enriches that: it states the call is not purely read-only, creates an XBOSS job per call, consumes 9 tokens, and stores results. It also discloses that computed=null means the result could not be assembled (read computed_error), that partial=true signals incompleteness in two different envelope shapes, that download_url expires in 15 minutes while files persist 7 days, and the full recovery_receipt rules for anonymous results.

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 text is a wall of run-on sentences that switches between Korean and English mid-paragraph, and critical warnings (partial, computed_error) are buried in the middle rather than front-loaded. File-lifetime and receipt rules consume substantial length before the reader reaches anything about which arguments matter. Much is genuinely useful content, but the packaging obscures it.

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 return-shape burden and largely does: computed, computed_error, partial, warnings, axes.notes_ko, and artifacts[].download_url are all explained, along with the recovery path via xdata__job__result. It is close to complete, missing only a sense of the response size or latency profile.

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 all eleven parameters, including the axes enum semantics, the start_dt/p_nm pairing, and the sDate/eDate defaults. The description largely restates those same rules rather than adding new meaning. Baseline 3 applies when the schema carries the weight.

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: it queries five axes (상태, 위험, 고용, 재무, 사업장) keyed off a single 사업자등록번호 and merges them into one sheet, and it enumerates the eleven fragments pulled in. That is far more concrete than the title alone. The one gap is that it never mentions the sibling tool company_info_pack__brief_v1__generate, so an agent cannot tell from this text alone which of the two pack generators to pick.

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?

There is real conditional guidance: axes selection changes which fragments become mandatory, an empty axes leaves only 사업자 상태 required, 진위확인 is included only when start_dt and p_nm are both sent, and an empty construction-sanction window defaults to the last year. However, no guidance distinguishes this from the brief_v1 sibling or from direct opendata lookups, and there is no explicit statement of when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources