Skip to main content
Glama

사업장 건물 조회

opendata__bld__register

공공데이터포털에 개방된 건축물대장 표제부(data.go.kr 15134735)를 주소로 조회합니다. 주소를 도로명주소 검색으로 지번에 맞춘 뒤 그 지번의 건물(동)마다 건물명, 주용도, 구조, 연면적, 층수, 사용승인일, 승강기 수, 내진설계 여부 등을 buildings 에 돌려주고, 찾은 주소 후보는 address 에, 대표 건물은 primary 에 담습니다. 사업자등록번호만 주면 등록된 소재지를 찾아 조회합니다. 별도 연동 없이 사용할 수 있습니다. 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__bld__register"
  }
}

Input Schema

NameRequiredDescriptionDefault
biznoNo사업자등록번호 10자리(하이픈 허용). address 가 없을 때 등록된 소재지를 찾는 데 씁니다.
pageNoNo페이지 번호(선택, 기본 1).
addressNo사업장 주소(도로명 또는 지번, 건물번호까지). address 와 bizno 가운데 하나 이상.
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

A3.5/5.0
Behavior4/5

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

With readOnlyHint=false and openWorldHint=true already declared, the description still adds substantial context: each call consumes one token, creates an XBOSS job whose result is persisted regardless of the upstream source, and is explicitly not a pure read-only operation. It also discloses artifact lifetime (15-minute download links, 7-day file retention) and the recovery-receipt rules, which are real behavioral facts an agent cannot infer from annotations.

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

Conciseness2/5

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

The first two sentences are well front-loaded, but the body then dumps a long generic English block about artifacts, recovery_receipt, idempotency keys and provider-specific keys that is boilerplate detached from this building-registry lookup. Mixed Korean/English and repetition about keys and receipts make it far longer than needed for a six-parameter lookup.

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?

No output schema exists, yet the description names the response buckets (buildings, address, primary) and the fields inside them, which is exactly what an agent needs for result handling. Cost, persistence and expiry behavior are covered; only edge behavior such as empty results or address-matching failures is unaddressed.

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 (bizno, address, pageNo, numOfRows, output_formats, request_idempotency_key) is already documented inline. The description only restates the address/bizno dependency and repeats the idempotency-key contract, adding little 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?

States a concrete verb and resource: queries 건축물대장 표제부 (data.go.kr 15134735) by address and returns building-name, use, structure, area, floors, approval date, elevator count and seismic design into 'buildings', plus 'address' and 'primary'. It is specific enough to distinguish from unrelated opendata siblings, though it does not explicitly contrast with same-family lookup tools.

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?

Gives partial routing rules (address OR bizno with at least one required; bizno alone resolves the registered workplace address) and says no separate integration is needed. It also names xdata__job__result as the fallback when a download link expires, but never states when to prefer this tool over other lookup paths, so guidance is implied rather than explicit.

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