Skip to main content
Glama

사업자 서류 판독(OCR)

business_doc_ocr
Read-only

Read a Korean business registration certificate, e-commerce (mail-order) business registration certificate, corporate registry certificate or seal certificate image and return each field (registration number, business name, representative, address, issue date, officers). Resident registration numbers are masked. Optionally checks the current business status. 사업자등록증·통신판매업 신고증·법인 등기사항증명서·인감증명서 사진에서 등록번호·상호·대표자·주소·발급일·임원을 항목별로 읽고, 등록번호 검증과 현재 사업자 상태 확인(check_status)을 함께 돌려줍니다. 주민등록번호는 뒤 6자리를 가립니다. [호출당 20포인트]

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": {
      "image_url": "<image_url>"
    },
    "name": "business_doc_ocr"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_typeNo문서 종류: auto(기본, 자동 판별) · business_registration(사업자등록증) · ecommerce_registration(통신판매업 신고증) · corporate_registry(법인 등기사항증명서) · seal_certificate(인감증명서)
image_urlYes다운로드 가능한 https URL (허용 형식: image/png, image/jpeg) (최대 50MB)
check_statusNo1 이면 사업자등록번호로 현재 사업자 상태(계속·휴업·폐업)와 과세유형을 함께 확인 (추가 요금 없음, 등기부·인감증명서는 조회 안 함)
include_textNo1 이면 판독한 전체 글자(text)도 함께 반환

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / check_status / description
      Previous value: -"1 이면 사업자등록번호로 현재 사업자 상태(계속·휴업·폐업)와 과세유형을 함께 확인 (추가 요금 없음)"New value: +"1 이면 사업자등록번호로 현재 사업자 상태(계속·휴업·폐업)와 과세유형을 함께 확인 (추가 요금 없음, 등기부·인감증명서는 조회 안 함)"
    • changedInput schema / properties / doc_type / description
      Previous value: -"문서 종류: auto(기본, 자동 판별) · business_registration(사업자등록증) · ecommerce_registration(통신판매업 신고증)"New value: +"문서 종류: auto(기본, 자동 판별) · business_registration(사업자등록증) · ecommerce_registration(통신판매업 신고증) · corporate_registry(법인 등기사항증명서) · seal_certificate(인감증명서)"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses privacy masking of resident registration numbers, a per-call cost of 20 points, and that the status check is free and skipped for registry/seal documents. These are real behavioral facts not visible in annotations. It does not describe failure modes for unreadable or unsupported images, which keeps it below 5.

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 core purpose is front-loaded, but the entire description is duplicated in English and Korean with near-identical content and the same field list and cost note, roughly doubling length. Deliberate bilingualism may be useful for a Korean-facing service, yet half the text earns no new information for the agent.

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 4 fully documented parameters, annotations present, and no output schema, the description covers the essentials an agent needs: accepted document types, returned fields, masking behavior, cost, and the optional status lookup. Only error/edge behavior and image-permission requirements are left unspecified.

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 baseline 3 applies. The description reinforces check_status semantics ('optionally checks the current business status') and document coverage, but adds nothing about include_text or the image_url format/size limits beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb ('Read') plus an explicit enumeration of the supported document types (사업자등록증, 통신판매업 신고증, 법인 등기사항증명서, 인감증명서) and the fields returned (registration number, business name, representative, address, issue date, officers). An agent can distinguish this from a generic OCR sibling or registry_doc_verify without opening any schema.

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?

Usage is implied by the enumerated document types and by noting that check_status additionally queries current business status. There is no explicit statement of when to prefer this over the similarly named siblings (ocr, ocr_identi*, registry_doc_verify) or any exclusion conditions, so the agent must infer the fit.

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.