Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

나라장터 부정당업자 제재 조회

opendata__g2b__sanction
Read-only

Look up G2B (나라장터) unfair-supplier sanction records (data.go.kr 15129466 getUnptRsttCorpInfo02, inqryDiv=1 + bizno). Empty upstream rows mean no matching record in this API response — not a certified 'no sanction ever' claim. Platform service key only — no account_link_id. 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자리(예: "1234567890"). 하이픈은 서버가 지운다.
pageNoNo페이지 번호(기본 1).
numOfRowsNo페이지당 행 수(기본 100, 최대 100).
inqryBgnDtNo조회 시작 일시 YYYYMMDDHHMM(선택).
inqryEndDtNo조회 종료 일시 YYYYMMDDHHMM(선택).
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. Changed5 schema fields changed
    • changedInput schema / properties / bizno / description
      Previous value: -"Business registration number, 10 digits (e.g. \"1234567890\"). Hyphens are stripped server-side."New value: +"사업자등록번호 10자리(예: \"1234567890\"). 하이픈은 서버가 지운다."
    • changedInput schema / properties / inqryBgnDt / description
      Previous value: -"Optional inquiry begin datetime YYYYMMDDHHMM."New value: +"조회 시작 일시 YYYYMMDDHHMM(선택)."
    • changedInput schema / properties / inqryEndDt / description
      Previous value: -"Optional inquiry end datetime YYYYMMDDHHMM."New value: +"조회 종료 일시 YYYYMMDDHHMM(선택)."
    • changedInput schema / properties / numOfRows / description
      Previous value: -"Rows per page (default 100, max 100)."New value: +"페이지당 행 수(기본 100, 최대 100)."
    • changedInput schema / properties / pageNo / description
      Previous value: -"Page number (default 1)."New value: +"페이지 번호(기본 1)."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive, but the description adds meaningful behavior: empty upstream rows are not proof of no sanction, platform service key only with no account_link_id, idempotency key recovery semantics, and one token consumed per call.

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

Conciseness4/5

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

The purpose and key caveats are front-loaded, but the idempotency guidance spans several somewhat repetitive sentences. It remains appropriately detailed for an authenticated, token-costing lookup, though it could be tighter.

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?

For a read-only lookup with no output schema, the description covers the data source, empty-result meaning, authentication, idempotency, and call cost. It does not describe returned fields or pagination behavior beyond what the schema already states, leaving a minor gap.

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 baseline is 3, and the schema already documents bizno, pagination, and date filters. The description adds substantial semantics for the optional request_idempotency_key, including when to reuse it and how it differs from provider-specific keys.

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') and resource ('G2B unfair-supplier sanction records'), including the upstream API identifier. The G2B scope distinguishes it from sibling opendata sanction tools such as waste and KISCON sanctions.

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?

Provides clear context for use: a bizno-based G2B sanction lookup, with caveats for empty rows and prerequisites around authentication and idempotency. It does not explicitly route the agent away from sibling sanction lookups, so it falls short of a full when/when-not/alternatives statement.

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