Skip to main content
Glama

사업장폐기물 행정처분 조회

opendata__env__waste_sanction

공공데이터포털에 개방된 사업장폐기물 행정처분 정보(data.go.kr 15156661)를 주기적으로 받아 둔 색인에서 사업자등록번호(bizno)로 조회합니다. 조회할 때 기관에 실시간으로 묻지 않습니다. matches 가 비어 있으면 조회 시점에 유효한 처분 기록을 찾지 못한 것이고, 처분이 없다는 확인서는 아닙니다. 별도 연동 없이 사용할 수 있습니다. 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__env__waste_sanction"
  }
}

Input Schema

NameRequiredDescriptionDefault
biznoYes사업자등록번호 10자리.
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

B3.4/5.0
Behavior3/5

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

The description goes beyond the annotations by disclosing that each call consumes one token, creates an XBOSS job and stores results, and that the call is not purely read-only despite reading cached data — consistent with readOnlyHint=false. It also details file retention (15-minute download links, 7-day retention) and recovery-receipt rules. That said, much of this is dense boilerplate about artifacts and receipts rather than the core lookup behavior.

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 key lookup semantics and the empty-result caveat are front-loaded, which is good. However, the body is long, mixes Korean and English, and devotes several sentences to generic receipt/file/idempotency boilerplate that dilutes the core message.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explain that results contain 'matches', artifacts with expiring download URLs, and a recovery receipt, and it names the follow-up tool (xdata__job__result) for expired links. It nonetheless never says what fields a match contains or how many records to expect, leaving a gap for a data-lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents bizno and output_formats, but the description supplies the idempotency-key semantics the schema only points to: generate before the first authenticated request, reuse only to recover a lost response, use a new key for a new execution, and unavailable for anonymous calls. It adds little beyond the schema for bizno itself.

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: lookup of workplace-waste administrative dispositions by business registration number, sourced from a periodically refreshed index of data.go.kr dataset 15156661. It also distinguishes the data path from real-time agency queries, which helps separate it from a live-lookup sibling. It does not name the other sanction-lookup siblings (g2b, kiscon), so it stops 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 Guidelines3/5

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

It gives useful interpretive guidance (empty 'matches' means no valid record at query time, not a certificate of no violation) and notes no separate integration is needed. However, there is no explicit statement of when to prefer this over the other sanction tools or what conditions make it unsuitable.

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