Skip to main content
Glama

법인 등기 열람·발급

registry_corporate_jobs_create
Idempotent

View and issue a corporate registry certificate in one call. 법인등록번호로 열람·발급을 끝내고 PDF 를 돌려줍니다. 최대 180초까지 걸릴 수 있습니다. 열람(view) 850P, 발급(issue) 1250P(PDF 전송 포함), 2026-11-23 00:00(KST)부터 열람 1300P · 발급 1700P. 발급이 실패하면 같은 job_id 로 결과 조회(POST /rest/registry_jobs/:job_id/download)를 호출할 때 접수 때 차감한 금액을 환급합니다. 결과 조회를 하지 않으면 환급되지 않고, 접수 후 24시간이 지난 조회는 환급되지 않습니다. 이미 발급한 PDF는 응답 헤더 X-Apick-Job-Id 를 job_id 로 POST /rest/registry_jobs/:job_id/download 에 보내 다시 받을 수 있습니다(건당 30P, 횟수 제한 없음). [호출당 850포인트]

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": "registry_corporate_jobs_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo검색 결과 행 번호(1부터), 기본 1
usageNo열람(view)·발급(issue), 기본 view
biz_noNo사업자등록번호 10자리(corp_reg_no가 없을 때)
corp_reg_noNo법인등록번호 13자리
idempotency_keyNo중복 결제 방지 키. 같은 키로 다시 호출하면 기존 작업의 PDF를 받습니다

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"중복 접수·과금 방지 키"New value: +"중복 결제 방지 키. 같은 키로 다시 호출하면 기존 작업의 PDF를 받습니다"
  2. Added

TDQS

A4/5.0
Behavior5/5

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

It adds substantial behavior beyond the annotations: a possible 180-second duration, explicit point costs with a future price change, an unusual refund rule that depends on calling the download endpoint within 24 hours, and a re-download path that costs 30P per item. It also explains that the response returns a PDF and that the job id comes back in the X-Apick-Job-Id header. The annotations (readOnlyHint=false, idempotentHint=true) are consistent with the description and are well supplemented.

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?

Pricing, latency, and refund policy are front-loaded and worth keeping, but the text is long and switches repeatedly between Korean and English, which makes it harder to scan. The trailing '[호출당 850포인트]' also conflicts with the earlier 1250P issue price, creating a redundant and confusing restatement.

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 covers the return shape at a useful level (a PDF, plus a job id in a response header) and covers latency, cost, and refund. It does not describe the failure response body or how a create-only call differs from the download endpoint, but nothing essential for correct invocation is missing.

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 index, usage, biz_no, corp_reg_no, and idempotency_key. The description reinforces the corporate registration number and the view vs issue enum with pricing but adds no format or syntax detail beyond the schema. 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 specific verb and resource ('View and issue a corporate registry certificate in one call') and states the key input (법인등록번호) and the returned artifact (PDF). It does not contrast itself with the sibling registry_corporate_search, so an agent must infer that search is a different, non-job call — the only remaining gap at this level.

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 clearly distinguishes the two modes of operation (열람 view vs 발급 issue) and gives the cost of each, which lets an agent pick a mode by intent and budget. It also spells out the failure/refund path. It stops short of naming a sibling alternative or explicitly saying when not to use this tool.

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.