Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

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

opendata__env__waste_sanction
Read-only

Look up workplace waste administrative disposition rows (data.go.kr 15156661) from the local batch M1 index by bizno/brno. Upstream getlist accepts bzentyNm/admdspYmd only — not brno; No live bizno GET is made. Empty matches mean no non-expired index row — not a certified clean claim. Platform service key only — no account_link_id. 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소진

Input Schema

NameRequiredDescriptionDefault
biznoYes사업자등록번호 10자리. 로컬 색인의 brno 와 대조한다.
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / output_formats
      Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / bizno / description
      Previous value: -"Business registration number, 10 digits. Matched against local index brno."New value: +"사업자등록번호 10자리. 로컬 색인의 brno 와 대조한다."
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real behavior: the data comes from a batch index, empty results mean 'no non-expired index row' rather than a clean certification, files expire after 15 minutes and are retained 7 days, and recovery uses xdata__job__result with a job_id. The only weakness is that much of this (receipt, idempotency, artifact) is generic boilerplate likely shared across many tools, diluting tool-specific disclosure.

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 the key 'empty matches are not a clean claim' caveat are front-loaded, which is good. But the middle section is a long, dense run-on about recovery receipts, idempotency and token cost that is largely reusable boilerplate and obscures the tool-specific guidance.

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?

There is no output schema, and the description never says what fields a disposition row contains or whether results are paginated or date-filtered, which an agent would want for planning. It does compensate somewhat by explaining artifacts and how to refresh expired download links via xdata__job__result.

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 bizno, output_formats and request_idempotency_key. The description adds only a small nuance: that upstream getlist does not accept brno, explaining why bizno is matched against the local index. Baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb (look up), resource (workplace waste administrative disposition rows), the upstream dataset id (15156661), and the index source (local batch M1 by bizno/brno). An agent can distinguish it from opendata__g2b__sanction and opendata__kiscon__sanction, which cover different sanction domains.

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?

Useful context is given (no live bizno GET; upstream only accepts bzentyNm/admdspYmd; platform service key only, no account_link_id), which implies when this tool is the right one. However, it never explicitly routes the agent between this and its sanction siblings, so selection remains inferred from naming rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources