Skip to main content
Glama

국민연금 가입 사업장 조회

opendata__nps__workplace

공공데이터포털에 개방된 국민연금 가입 사업장 정보(data.go.kr 3046071)를 사업자등록번호와 상호로 조회합니다. 원천이 사업자등록번호를 앞 6자리만 제공하므로 candidates 에는 같은 앞자리의 다른 사업장이 섞일 수 있고, 상호가 정확히 일치하는 사업장만 matched 에 가입자수, 당월고지금액, 사업장등록일, 탈퇴일, 업종을 함께 돌려줍니다. 가입자 3인 이상 법인과 10인 이상 개인사업장만 개방되어 빈 결과가 미가입을 뜻하지는 않습니다. 별도 연동 없이 사용할 수 있습니다. 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

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

Input Schema

NameRequiredDescriptionDefault
biznoYes사업자등록번호 10자리(하이픈 허용). 앞 6자리로 후보를 찾습니다.
pageNoNo후보 페이지 번호(선택, 기본 1).
wkplNmNo사업장 상호(선택). 비우면 법인 상호를 기업개요에서 찾아 씁니다. 사업자등록증의 상호를 그대로 주면 가장 정확합니다.
numOfRowsNo후보 한 페이지 행 수(선택, 기본 100).
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations it discloses that each call consumes one token, spawns an XBOSS job and persists the result, and explicitly states the call is not purely read-only — consistent with readOnlyHint=false. It also documents file behavior (xlsx only on request, in artifacts[], 15-minute download URL, 7-day retention), anonymous-result recovery_receipt semantics, and idempotency-key reuse rules.

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?

Purpose and matching semantics are front-loaded in the first sentences, which is good. However the body is padded with a long block of cross-cutting boilerplate (artifacts, recovery receipts, idempotency keys, token accounting) that buries the tool-specific content and makes the definition read as several unrelated paragraphs.

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 does the work of describing return structure: candidates vs matched, and the fields returned in matched (가입자수, 당월고지금액, 사업장등록일, 탈퇴일, 업종), plus artifact listing. It falls short of describing the candidate record shape or what paging metadata comes back.

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 explains bizno prefix matching, wkplNm fallback to the corporate name, paging, and output_formats. The description restates the prefix/candidate caveat and the artifact mechanics but adds little syntax or meaning the schema does not already carry, so the baseline 3 applies.

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 opening sentence names a specific verb and resource (국민연금 가입 사업장 정보 조회) and pins the exact data source (data.go.kr 3046071) with the lookup keys (사업자등록번호, 상호). It further specifies the matching contract — 6-digit prefix candidates vs exact-name matched records — so an agent knows precisely what this tool returns.

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 gives real context for use: no separate integration is needed, coverage is limited to corporations with 3+ subscribers and sole proprietors with 10+, and an empty result does not mean non-enrollment. It also routes the agent to xdata__job__result when a download link expires. What it lacks is any explicit comparison against related siblings (e.g. opendata__comwel__workplace or the nps_edi workplace lookups).

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