Skip to main content
Glama

APICK

by app.apick
OverviewDiscussionsAdmin

사업자 정보 조회

biz_detail
Read-only

Look up general status information of a Korean business by its 10-digit business registration number. 사업자등록번호로 해당 사업자의 일반 현황 정보(대표자, 주소, 직원수, 설립일, 업종, 업태, 종목, 연락처, 사업자상태, 과세유형 등)를 조회합니다. 법인은 financial_info=Y 로 기업재무정보(요약재무제표·재무상태표·손익계산서)를 추가 요금 없이 함께 받을 수 있습니다. [호출당 50포인트]

Input Schema

NameRequiredDescriptionDefault
biz_noYes사업자등록번호 (숫자 10자리, 하이픈 제외, 예: 1234567890)
financial_infoNoY 이면 법인의 기업재무정보(최근 3개 사업연도 요약재무제표, 최근 사업연도 재무상태표·손익계산서)를 기업재무정보 필드에 함께 반환합니다. 법인만 제공되며 추가 요금은 없습니다. 재무정보가 없으면 기업재무정보.조회결과=N 과 사유코드를 반환합니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / biz_no / description
      Previous value: -"사업자등록번호 (숫자 10자리, 하이픈 제외, 예: 4398700761)"New value: +"사업자등록번호 (숫자 10자리, 하이픈 제외, 예: 1234567890)"
    • addedInput schema / properties / financial_info
      Added value: +{
+  "description": "Y 이면 법인의 기업재무정보(최근 3개 사업연도 요약재무제표, 최근 사업연도 재무상태표·손익계산서)를 기업재무정보 필드에 함께 반환합니다. 법인만 제공되며 추가 요금은 없습니다. 재무정보가 없으면 기업재무정보.조회결과=N 과 사유코드를 반환합니다.",
+  "enum": [
+    "Y",
+    "N"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and external data access. The description adds important behavioral context beyond annotations: a cost of '[호출당 50포인트]' per call and that financial_info=Y returns corporate financial data at no extra charge. It does not contradict the annotations.

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

Conciseness4/5

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

The purpose is front-loaded in the first sentence and the cost is placed last. The Korean sentence largely duplicates the English purpose, which adds length without new information for non-Korean readers, but the structure is otherwise efficient.

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 usefully enumerates returned fields (대표자, 주소, 직원수, etc.) and covers cost and the optional financial_info behavior. It omits error-handling details beyond the financial_info case, but is otherwise complete for a simple read-only lookup.

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%, and both biz_no format and financial_info behavior are fully documented in the schema. The description repeats financial_info=Y but adds no syntax or format details beyond the schema, so the baseline of 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 states a specific verb ('Look up') and resource ('general status information of a Korean business'), keyed by the '10-digit business registration number', and lists returned fields. It does not explicitly differentiate itself from potential siblings such as venture_biz_info, so it falls short of 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool retrieves and what financial_info=Y does, but gives no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Like the calibration example for update_drive, usage is only implicitly inferable from the purpose.

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

All APICK 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