Skip to main content
Glama

기업개요 조회

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_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, and the description explicitly corroborates this by saying the call is not purely read-only, that it consumes one token, and that it creates an XBOSS job and stores the result. It goes further with artifact behavior (xlsx only when requested, 15-minute download URLs, 7-day retention), recovery paths via job_id or recovery_receipt, and idempotency-key reuse rules — context no structured field supplies.

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 returned-field list are front-loaded and efficient, but a large trailing block of generic boilerplate about receipts, idempotency keys, and job recovery is disproportionate to a simple lookup. That material is relevant to some calls but is not specific enough to this tool to justify its length here.

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 compensates by enumerating the returned fields and explaining the row/current semantics and pagination defaults. The remaining gaps are minor — no explicit error or empty-result behavior — but an agent has enough to call it correctly.

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 every parameter including crno, bizno, corpNm, pagination, output_formats and request_idempotency_key is already documented in the schema. The description adds the useful fact that multiple rows for one corporation are different disclosure snapshots with 'current' being the latest, but that is return-value semantics rather than parameter meaning, so the baseline 3 applies.

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 concrete verb and resource ('법인 기업개요 ... 조회'), cites the source dataset (data.go.kr 15043184), and enumerates the returned fields (법인명, 사업자등록번호, 설립일자, 업종, 상장 시장), so an agent knows exactly what this returns. It also rules out sole proprietorships, which separates it from generic business-status siblings, though it never names those siblings directly.

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 states that at least one of 상호/crno/bizno must be supplied and that no separate integration or login is required, which is useful setup context. However, it never says when to prefer this over opendata__nts__status or opendata__fsc__financials, so the routing decision to sibling tools is left implicit.

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